CVE-2026-50555: Angular: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in @angular/platform-server

Published Jun 15, 2026
·
Updated

A Cross-Site Scripting (XSS) vulnerability exists in @angular/platform-server's DOM emulation dependency (domino) when serializing the content of raw-text elements (such as <script>, <style>, and <iframe>).

domino supports escaping raw-text elements during serialization to prevent closing-tag breakout. However, a Unicode index alignment bug existed in this escaping logic.

In JavaScript, string lengths and character indices are calculated based on UTF-16 code units (where astral characters—such as emojis—occupy 2 code units / 4 bytes). If the bound dynamic text contained astral Unicode characters before the closing tag (e.g. </script>, </style>, or </iframe>), the index offset calculation in domino's replacement logic shifted.

This misalignment caused domino to fail to replace or escape the closing tag, leaving it raw and unescaped in the output HTML.

An attacker who controls the dynamic text can supply a payload containing both an astral Unicode character and a closing tag (e.g., 😀</iframe><script>alert(1)</script>). When serialized on the server during SSR, the browser parses the unescaped closing tag, exits the raw-text context early, and executes the subsequent <script> block, leading to same-origin Cross-Site Scripting (XSS).

Impact

This vulnerability allows an attacker to perform same-origin Cross-Site Scripting (XSS) attacks against any user visiting an SSR-rendered page that binds user-controlled data inside raw-text elements. This can lead to session hijacking, credentials theft, unauthorized actions on behalf of users, and defacement.

Patched Versions

- 22.0.0-rc.2 - 21.2.16 - 20.3.24 - 19.2.25

Workarounds

If you cannot immediately update your dependencies, you can:

- Avoid binding user-controlled values inside <iframe> or other raw-text elements. - Sanitize any user input placed inside raw-text elements to explicitly strip closing tags before passing it to the template.

Other sources

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-rc.2, 21.2.16, 20.3.24, and 19.2.25, a Cross-Site Scripting (XSS) vulnerability exists in @angular/platform-server's DOM emulation dependency (domino) when serializing the content of raw-text elements (such as <script>, <style>, and <iframe>). domino supports escaping raw-text elements during serialization to prevent closing-tag breakout. However, a Unicode index alignment bug existed in this escaping logic. In JavaScript, string lengths and character indices are calculated based on UTF-16 code units (where astral characters—such as emojis—occupy 2 code units / 4 bytes). If the bound dynamic text contained astral Unicode characters before the closing tag (e.g. </script>, </style>, or </iframe>), the index offset calculation in domino's replacement logic shifted. This misalignment caused domino to fail to replace or escape the closing tag, leaving it raw and unescaped in the output HTML. An attacker who controls the dynamic text can supply a payload containing both an astral Unicode character and a closing tag (e.g., 😀</iframe><script>alert(1)</script>). When serialized on the server during SSR, the browser parses the unescaped closing tag, exits the raw-text context early, and executes the subsequent <script> block, leading to same-origin Cross-Site Scripting (XSS). This vulnerability is fixed in 22.0.0-rc.2, 21.2.16, 20.3.24, and 19.2.25.

MITRE

Affected Software

24 affected componentsFixes available
npm/@angular/platform-server<=18.2.14
npm/@angular/platform-server>=19.0.0-next.0<19.2.25
19.2.25
npm/@angular/platform-server>=20.0.0-next.0<20.3.24
20.3.24
npm/@angular/platform-server>=21.0.0-next.0<21.2.16
21.2.16
npm/@angular/platform-server>=22.0.0-next.0<22.0.0-rc.2
22.0.0-rc.2
angular Angular Node.js<=18.2.14
angular Angular Node.js>=19.0.0<19.2.25
angular Angular Node.js>=20.0.0<20.3.24
angular Angular Node.js>=21.0.0<21.2.6
angular Angular Node.js=22.0.0-next0
angular Angular Node.js=22.0.0-next1
angular Angular Node.js=22.0.0-next10
angular Angular Node.js=22.0.0-next11
angular Angular Node.js=22.0.0-next12
angular Angular Node.js=22.0.0-next2
angular Angular Node.js=22.0.0-next3
angular Angular Node.js=22.0.0-next4
angular Angular Node.js=22.0.0-next5
angular Angular Node.js=22.0.0-next6
angular Angular Node.js=22.0.0-next7
angular Angular Node.js=22.0.0-next8
angular Angular Node.js=22.0.0-next9
angular Angular Node.js=22.0.0-rc0
angular Angular Node.js=22.0.0-rc1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/@angular/platform-server to a version that resolves this vulnerability.

    Fixed in 19.2.25
  2. Upgrade

    Upgrade npm/@angular/platform-server to a version that resolves this vulnerability.

    Fixed in 20.3.24
  3. Upgrade

    Upgrade npm/@angular/platform-server to a version that resolves this vulnerability.

    Fixed in 21.2.16
  4. Upgrade

    Upgrade npm/@angular/platform-server to a version that resolves this vulnerability.

    Fixed in 22.0.0-rc.2
  5. Upgrade

    Upgrade @angular/platform-server/domino to a version that resolves this vulnerability.

    Fixed in 19.2.25
  6. Upgrade

    Upgrade @angular/platform-server/domino to a version that resolves this vulnerability.

    Fixed in 20.3.24
  7. Upgrade

    Upgrade @angular/platform-server/domino to a version that resolves this vulnerability.

    Fixed in 21.2.16
  8. Upgrade

    Upgrade @angular/platform-server/domino to a version that resolves this vulnerability.

    Fixed in 22.0.0-rc.2
  9. Configuration

    If user-controlled content must be used in raw-text elements, sanitize it to explicitly strip closing tags before passing it to the template to prevent closing-tag breakout (e.g., before <script>/<style>/<iframe> serialization).

    Application template rendering (SSR) User input sanitization for raw-text elements = Explicitly strip closing tags before passing user-controlled data to the template
  10. Compensating control

    Avoid binding user-controlled values inside raw-text elements such as <script>, <style>, and <iframe> when using SSR with @angular/platform-server's DOM emulation dependency (domino).

Event History

Jun 15, 2026
Advisory Published
via GitHub·05:20 PM
Data Sourced
via GitHub·05:20 PM
DescriptionWeaknessAffected Software
Jun 22, 2026
CVE Published
via MITRE·03:37 PM
Data Sourced
via MITRE·03:37 PM
DescriptionWeakness
Data Sourced
via NVD·06:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-50555?

CVE-2026-50555 has a high severity rating of 8.6 according to the CVSS scoring system.

2

What is CVE-2026-50555 vulnerability?

CVE-2026-50555 is a Cross-Site Scripting (XSS) vulnerability in the `@angular/platform-server` component due to improper input neutralization during web page generation.

3

How can I fix CVE-2026-50555?

To mitigate CVE-2026-50555, ensure that you update to the latest version of `@angular/platform-server` that includes the security patch for this vulnerability.

4

What software is affected by CVE-2026-50555?

CVE-2026-50555 affects the AngularJS framework, specifically the `@angular/platform-server` module.

5

What type of attack does CVE-2026-50555 facilitate?

CVE-2026-50555 facilitates a Cross-Site Scripting (XSS) attack, allowing attackers to inject malicious scripts into web pages.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203