Answer in brief
CVE-2026-50556 records a High severity (CVSS 8.6) xss vulnerability in @angular/platform-server: Missing `<noscript>` Raw-Text Serialization Escaping leads to Cross-Site Scripting (XSS) in Angular SSR. The source record does not mark it as known exploited. 5 affected packages are mapped in the feed.
Answer in brief
CVE-2026-50556 records a High severity (CVSS 8.6) xss vulnerability in @angular/platform-server: Missing `<noscript>` Raw-Text Serialization Escaping leads to Cross-Site Scripting (XSS) in Angular SSR. The source record does not mark it as known exploited. 5 affected packages are mapped in the feed.
Update @angular/platform-server to 21.2.16; @angular/platform-server to 20.3.24; @angular/platform-server to 19.2.25; @angular/platform-server to 22.0.0-rc.2 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanXSS describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-50556 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| @angular/platform-servernpm | >=21.0.0-next.0,<21.2.16 | 21.2.16 |
| @angular/platform-servernpm | >=20.0.0-next.0,<20.3.24 | 20.3.24 |
| @angular/platform-servernpm | >=19.0.0-next.0,<19.2.25 | 19.2.25 |
| @angular/platform-servernpm | <=18.2.14 | Not reported |
| @angular/platform-servernpm | >=22.0.0-next.0,<22.0.0-rc.2 | 22.0.0-rc.2 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-50556 records a High severity (CVSS 8.6) xss vulnerability in @angular/platform-server: Missing `<noscript>` Raw-Text Serialization Escaping leads to Cross-Site Scripting (XSS) in Angular SSR. The source record does not mark it as known exploited. 5 affected packages are mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for @angular/platform-server, @angular/platform-server, @angular/platform-server.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate @angular/platform-server to 21.2.16; @angular/platform-server to 20.3.24; @angular/platform-server to 19.2.25; @angular/platform-server to 22.0.0-rc.2 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanXSS describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-50556 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| @angular/platform-servernpm | >=21.0.0-next.0,<21.2.16 | 21.2.16 |
| @angular/platform-servernpm | >=20.0.0-next.0,<20.3.24 | 20.3.24 |
| @angular/platform-servernpm | >=19.0.0-next.0,<19.2.25 | 19.2.25 |
| @angular/platform-servernpm | <=18.2.14 | Not reported |
| @angular/platform-servernpm | >=22.0.0-next.0,<22.0.0-rc.2 | 22.0.0-rc.2 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-50556 records a High severity (CVSS 8.6) xss vulnerability in @angular/platform-server: Missing `<noscript>` Raw-Text Serialization Escaping leads to Cross-Site Scripting (XSS) in Angular SSR. The source record does not mark it as known exploited. 5 affected packages are mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for @angular/platform-server, @angular/platform-server, @angular/platform-server.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardA 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.
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). ### 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.