Angular: Missing `<noscript>` Raw-Text Serialization Escaping leads to Cross-Site Scripting (XSS) in Angular SSR
angular
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @angular/platform-server npm |
|
|
angular
| Product | Affected | Fixed in |
|---|---|---|
| @angular/platform-server npm |
|
|
19.2.25Angular 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.
From the CVE record · GitHub_M
An XSS flaw in @angular/platform-server's DOM emulation dependency can leave a closing </noscript> tag unescaped during server-side rendering. If attacker-controlled text is bound inside a <noscript> element, injected script can execute in a user's browser when they view the rendered page; authentication requirements are not specified.
Teams running npm @angular/platform-server in the affected ranges—>=22.0.0-next.0 <22.0.0-rc.2, >=21.0.0-next.0 <21.2.16, >=20.0.0-next.0 <20.3.24, >=19.0.0-next.0 <19.2.25, or <=18.2.14—should check their deployments.