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 SSR: Missing Fallback Raw-Content Serialization Escaping leads to Cross-Site Scripting (XSS)

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_V4 Publisher rating HIGHFixed by @angular/platform-server 22.0.7Fixed by @angular/platform-server 21.2.19Fixed by @angular/platform-server 20.3.27KEV status unknown

cve-program · CVE-2026-69149

Published

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.27, 21.2.19, and 22.0.7, a Cross-Site Scripting (XSS) vulnerability exists in @angular/platform-server's DOM emulation dependency (domino) when serializing the content of fallback raw-content elements (<iframe>, <noembed>, <noframes>, and <noscript>). This issue is fixed in versions 20.3.27, 21.2.19, and 22.0.7.

Read the publisher's advisory

euvd · EUVD-2026-52350

Published

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.27, 21.2.19, and 22.0.7, a Cross-Site Scripting (XSS) vulnerability exists in @angular/platform-server's DOM emulation dependency (domino) when serializing the content of fallback raw-content elements (<iframe>, <noembed>, <noframes>, and <noscript>). This issue is fixed in versions 20.3.27, 21.2.19, and 22.0.7.

Read the publisher's advisory

nvd · CVE-2026-69149

Published

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.27, 21.2.19, and 22.0.7, a Cross-Site Scripting (XSS) vulnerability exists in @angular/platform-server's DOM emulation dependency (domino) when serializing the content of fallback raw-content elements (<iframe>, <noembed>, <noframes>, and <noscript>). This issue is fixed in versions 20.3.27, 21.2.19, and 22.0.7.

Read the publisher's advisory

osv · GHSA-vpx6-8pjr-4g3v

Published

A Cross-Site Scripting (XSS) vulnerability exists in `@angular/platform-server`'s DOM emulation dependency (`domino`) when serializing the content of fallback raw-content elements (`<iframe>`, `<noembed>`, `<noframes>`, and `<noscript>`). When rendering dynamic text content inside fallback raw-content elements via template bindings, the template engine expects the browser to render the content safely. Under Server-Side Rendering (SSR), `domino` is configured with scripting enabled, meaning these elements are treated as raw-text elements. However, `domino`'s serializer previously did not escape text nodes within fallback raw-content elements (`<iframe>`, `<noembed>`, `<noframes>`, `<noscript>`) during DOM serialization. As a result, any occurrence of closing tags in the bound dynamic text was not escaped. The unescaped closing tag could be serialized directly into the output HTML. When parsed by a browser or re-parsed during SSR post-processing without preserving raw-content parser state, an injected closing tag closes the element early, allowing an 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 fallback raw-content elements (`<iframe>`, `<noembed>`, `<noframes>`, `<noscript>`). This can lead to session hijacking, credentials theft, unauthorized actions on behalf of users, and defacement. ### Patched Versions - 22.0.7 - 21.2.19 - 20.3.27 ### Workarounds If you cannot immediately update your dependencies, you can mitigate this issue using any of the following approaches: - **Disable critical CSS inlining**: Critical CSS inlining in Angular SSR post-processes the rendered HTML using `domino`. Disabling this step prevents `domino` from re-parsing and re-serializing the HTML during server-side rendering. - In `angular.json`, set `inlineCritical` to `false` under style optimization options: ```json { "projects": { "my-app": { "architect": { "build": { "builder": "@angular/build:application", "options": { "optimization": { "styles": { "inlineCritical": false } } } } } } } } ``` - When rendering programmatically with `CommonEngine`, set `inlineCriticalCss: false` in your render options. - **Avoid binding user-controlled values** inside fallback raw-content elements (`<iframe>`, `<noembed>`, `<noframes>`, `<noscript>`). - **Sanitize user input** placed inside these elements to explicitly strip or escape closing tags before passing it to the template.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-69149

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": "< 20.3.27",
                            "status": "affected"
                        },
                        {
                            "version": ">= 21.0.0-next.0, < 21.2.19",
                            "status": "affected"
                        },
                        {
                            "version": ">= 22.0.0-next.0, < 22.0.7",
                            "status": "affected"
                        }
                    ]
                }

platform-server

Vendor product

Publisher's version information

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

{
                    "vendor": "@angular",
                    "product": "platform-server",
                    "versions": [
                        {
                            "version": "< 20.3.27",
                            "status": "affected"
                        },
                        {
                            "version": ">= 21.0.0-next.0, < 21.2.19",
                            "status": "affected"
                        },
                        {
                            "version": ">= 22.0.0-next.0, < 22.0.7",
                            "status": "affected"
                        }
                    ]
                }

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

euvd · EUVD-2026-52350

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: Aug 3, 2026, 4:14:39 PM

dateUpdated: Aug 3, 2026, 8:33:46 PM

1 related source bulletins · separate from aliases

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

CVE-2026-68945 · CVE-2026-69149 · CVE-2026-69151

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

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-08-03T17:16:45.627

lastModified: 2026-08-11T18:18:49.217

1 source CPE criteria · context only
  • cpe:2.3:a:angular:angular:*:*:*:*:*: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-vpx6-8pjr-4g3v

Published

@angular/platform-server

npm

SEMVER · introduced 22.0.0-next.0 → fixed 22.0.7

@angular/platform-server

npm

SEMVER · introduced 21.0.0-next.0 → fixed 21.2.19

@angular/platform-server

npm

SEMVER · introduced 20.0.0-next.0 → fixed 20.3.27

@angular/platform-server

npm

SEMVER · introduced 0 → last_affected 19.2.25

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 22 Nov 08:05 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current