CVE-2026-69149 — Angular SSR: Missing Fallback Raw-Content Serialization Escaping leads to Cross-Site Scripting (XSS)
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented mitigation — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Angular Angular, Angular Platform-server).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (cross-site scripting), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Angular | Angular | ≤ 19.2.25≥ 20.0.0 and < 20.3.27≥ 21.0.0 and < 21.2.19≥ 22.0.0 and < 22.0.7 | Vulnerable | NIST National Vulnerability Database |
| Angular | Angular | version < 20.3.27version >= 21.0.0-next.0, < 21.2.19version >= 22.0.0-next.0, < 22.0.7 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Angular | Platform-server | version < 20.3.27version >= 21.0.0-next.0, < 21.2.19version >= 22.0.0-next.0, < 22.0.7 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.6 | CVSS 4.0 | High | — | — | security-advisories@github.com via NIST National Vulnerability Database |
| 8.6 | CVSS 4.0 | High | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
| 6.1 | CVSS 3.1 | Medium | 2.8 | 2.7 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor CSP violation reports and script payloads in reflected parameters.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · angular/angular, @angular/platform-server
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 6.1
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
7 on the record
- github.com/angular/angular/security/advisories/GHSA-vpx6-8pjr-4g3v
- github.com/angular/domino/commit/f88e5aa49cf2804d7c2df22ef1640eb4ec43dd56
- github.com/angular/angular/pull/69714
- github.com/angular/domino/pull/32
- github.com/angular/angular/pull/69930
- github.com/angular/angular/pull/69929
- github.com/angular/angular/pull/69675
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-101897 Angular DevTools (Local DoS) 1d
- High CVE-2026-101896 Angular: Denial of Service via Numeric URL Matrix Parameters in Server-Side Rendering (SSR) 1d
- High CVE-2026-101895 Angular SSR: Denial of Service (DoS) via Infinite Loop on Malformed DOCTYPE 1d
- Medium CVE-2026-88060 Cross-site Scripting (XSS) in Angular Sep 10, 2026
- Critical CVE-2026-88056 Server-Side Request Forgery (SSRF) in Angular Sep 10, 2026
- Medium CVE-2026-88059 Exposure of Sensitive Information in Angular Sep 10, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-69149 is "Angular SSR: Missing Fallback Raw-Content Serialization Escaping leads to Cross-Site Scripting (XSS)", rated Medium. It affects Angular (Angular); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.1 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.