Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

angular · cross-site scripting

CVSS 4.0 8.6 HIGHEUVD CVSS 4.0 8.6 CVSS 4.0 · [email protected] · Secondary 8.6 HIGHCVSS 3.1 · [email protected] · Primary 6.1 MEDIUMCVSS 3.1 · 0b0ca135-0b70-47e7-9f44-1890c2a1c46c · Secondary 8.1 HIGHCVSS_V4 Publisher rating HIGHFixed by @angular/platform-server 22.0.0-rc.2Fixed by @angular/platform-server 21.2.16Fixed by @angular/platform-server 20.3.24Fixed by @angular/platform-server 19.2.25KEV status unknown

cve-program · CVE-2026-50556

Published

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 <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 advisory

euvd · EUVD-2026-38291

Published

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 <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 advisory

nvd · CVE-2026-50556

Published

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 <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 advisory

osv · GHSA-gxx4-3xcv-f8qx

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-50556

Published

angular

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "angular",
                    "product": "angular",
                    "versions": [
                        {
                            "version": ">= 22.0.0-next.0, < 22.0.0-rc.2",
                            "status": "affected"
                        },
                        {
                            "version": ">= 21.0.0-next.0, < 21.2.16",
                            "status": "affected"
                        },
                        {
                            "version": ">= 20.0.0-next.0, < 20.3.24",
                            "status": "affected"
                        },
                        {
                            "version": ">= 19.0.0-next.0, < 19.2.25",
                            "status": "affected"
                        },
                        {
                            "version": "<= 18.2.14",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-38291

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jun 22, 2026, 3:38:28 PM

dateUpdated: Jul 15, 2026, 12:46:49 AM

1 related source bulletins · separate from aliases

WID-SEC-W-2026-1930: Angular: Mehrere Schwachstellen

CVE-2026-50168 · CVE-2026-50169 · CVE-2026-50170 · CVE-2026-50171 · CVE-2026-50184 · CVE-2026-50555 · CVE-2026-50556 · CVE-2026-50557 · CVE-2026-52725 · CVE-2026-54264 · CVE-2026-54267

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-50556

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-79

Original publisher date fields

published: 2026-06-22T18:16:43.190

lastModified: 2026-07-15T01:16:19.880

16 source CPE criteria · context only
  • cpe:2.3:a:angular:angular:*:*:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next0:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next1:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next10:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next11:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next12:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next2:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next3:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next4:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next5:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next6:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next7:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next8:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next9:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:rc0:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:rc1:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-gxx4-3xcv-f8qx

Published

@angular/platform-server

npm

SEMVER · introduced 22.0.0-next.0 → fixed 22.0.0-rc.2

@angular/platform-server

npm

SEMVER · introduced 21.0.0-next.0 → fixed 21.2.16

@angular/platform-server

npm

SEMVER · introduced 20.0.0-next.0 → fixed 20.3.24

@angular/platform-server

npm

SEMVER · introduced 19.0.0-next.0 → fixed 19.2.25

@angular/platform-server

npm

SEMVER · introduced 0 → last_affected 18.2.14

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 00:16 UTC · 274 of 275 readable · 251 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current