CVE-2026-50555(angular / angular)

LOWCVSS 6.1 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

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.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-79

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • angular

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • 1 total mentions across 1 day

Affected systems

Vendors
Products
angular

1 version affected across 1 product

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-10-09: 110-09
Full discourse1 post
  • Abd El Rahman@x_harouat

    I used Opus 4.8 to find a high-severity XSS in Angular's SSR (CVE-2026-50555). The root cause was a Unicode bug in a dependency, but it broke out into Angular itself. Google closed my report as "Intended Behavior" with no bounty and no credit. Angular team rated it as high-severity in Github Advisories 😒 Lesson: a vulnerability doesn't have to come from the core project — sometimes it comes from a dependency and surfaces through it.

    0000044
    12 followersView on X
CPE platform detail16 entries

16 of 16 entries

PartVendorProductVersionTarget SWTarget HW
Appangularangular-node.js-
Appangularangular22.0.0node.js-
Appangularangular22.0.0node.js-
Appangularangular22.0.0node.js-
Appangularangular22.0.0node.js-
Appangularangular22.0.0node.js-
Appangularangular22.0.0node.js-
Appangularangular22.0.0node.js-
Appangularangular22.0.0node.js-
Appangularangular22.0.0node.js-
Appangularangular22.0.0node.js-
Appangularangular22.0.0node.js-
Appangularangular22.0.0node.js-
Appangularangular22.0.0node.js-
Appangularangular22.0.0node.js-
Appangularangular22.0.0node.js-

Explore more