angular · cross-site scripting
cve-program · CVE-2026-50556
PublishedAngular 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 <noscript> elements. When rendering dynamic text content inside a <noscript> element via template bindings (such as {{ value }} or [textContent]), the template engine expects the browser to render the content safely. Under Server-Side Rendering (SSR), domino is configured with scripting enabled, meaning <noscript> is treated as a raw-text element. However, domino's serializer completely omitted <noscript> from the list of raw-text elements requiring closing-tag escaping during DOM serialization. As a result, any occurrence of </noscript> in the bound dynamic text was never escaped under any circumstances. The unescaped closing tag was serialized directly into the output HTML (e.g. <noscript></noscript><script>alert(1)</script></noscript>). When parsed by a browser, it closes the <noscript> block early, allowing the injected <script> block to execute in the user's browser context, causing 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.
Read the publisher's advisoryeuvd · EUVD-2026-38291
PublishedAngular 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 <noscript> elements. When rendering dynamic text content inside a <noscript> element via template bindings (such as {{ value }} or [textContent]), the template engine expects the browser to render the content safely. Under Server-Side Rendering (SSR), domino is configured with scripting enabled, meaning <noscript> is treated as a raw-text element. However, domino's serializer completely omitted <noscript> from the list of raw-text elements requiring closing-tag escaping during DOM serialization. As a result, any occurrence of </noscript> in the bound dynamic text was never escaped under any circumstances. The unescaped closing tag was serialized directly into the output HTML (e.g. <noscript></noscript><script>alert(1)</script></noscript>). When parsed by a browser, it closes the <noscript> block early, allowing the injected <script> block to execute in the user's browser context, causing 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.
Read the publisher's advisorynvd · CVE-2026-50556
PublishedAngular 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 <noscript> elements. When rendering dynamic text content inside a <noscript> element via template bindings (such as {{ value }} or [textContent]), the template engine expects the browser to render the content safely. Under Server-Side Rendering (SSR), domino is configured with scripting enabled, meaning <noscript> is treated as a raw-text element. However, domino's serializer completely omitted <noscript> from the list of raw-text elements requiring closing-tag escaping during DOM serialization. As a result, any occurrence of </noscript> in the bound dynamic text was never escaped under any circumstances. The unescaped closing tag was serialized directly into the output HTML (e.g. <noscript></noscript><script>alert(1)</script></noscript>). When parsed by a browser, it closes the <noscript> block early, allowing the injected <script> block to execute in the user's browser context, causing 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.
Read the publisher's advisoryosv · GHSA-gxx4-3xcv-f8qx
PublishedA Cross-Site Scripting (XSS) vulnerability exists in `@angular/platform-server`'s DOM emulation dependency (`domino`) when serializing the content of `<noscript>` elements. When rendering dynamic text content inside a `<noscript>` element via template bindings (such as `{{ value }}` or `[textContent]`), the template engine expects the browser to render the content safely. Under Server-Side Rendering (SSR), `domino` is configured with scripting enabled, meaning `<noscript>` is treated as a raw-text element. However, `domino`'s serializer completely omitted `<noscript>` from the list of raw-text elements requiring closing-tag escaping during DOM serialization. As a result, any occurrence of `</noscript>` in the bound dynamic text was **never escaped under any circumstances**. The unescaped closing tag was serialized directly into the output HTML (e.g. `<noscript></noscript><script>alert(1)</script></noscript>`). When parsed by a browser, it closes the `<noscript>` block early, allowing the injected `<script>` block to execute in the user's browser context, causing 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 a `<noscript>` element. 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 `<noscript>` elements. - Sanitize any user input placed inside `<noscript>` to explicitly strip closing `</noscript>` tags before passing it to the template.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-50556 · CVE overview and exploitation status
cve-program · CVE-2026-50556
- https://github.com/angular/angular/security/advisories/GHSA-gxx4-3xcv-f8qx
- https://github.com/angular/angular/issues/68903
- https://github.com/angular/domino/pull/29
euvd · EUVD-2026-38291
- https://github.com/angular/angular/security/advisories/GHSA-gxx4-3xcv-f8qx
- https://github.com/angular/angular/issues/68903
- https://github.com/angular/domino/pull/29
nvd · CVE-2026-50556
- https://github.com/angular/angular/issues/68903
- https://github.com/angular/angular/security/advisories/GHSA-gxx4-3xcv-f8qx
- https://github.com/angular/domino/pull/29
- https://access.redhat.com/security/cve/CVE-2026-50556
- https://bugzilla.redhat.com/show_bug.cgi?id=2491459
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-50556.json