CVE-2026-69149

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 90% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 (, , , and ). This issue is fixed in versions 20.3.27, 21.2.19, and 22.0.7.

CVSS v3
6.1
EG Score
6.1(medium)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 11, 2026

Advisory Details (7)

Auto-updated Aug 3, 2026
Patch available. Sources: github, github_pr, github_commit.
github_commit

commit f88e5aa49cf2 (angular/domino)

Fix landed in angular/domino commit f88e5aa49cf2 — awaiting tagged release

https://github.com/angular/domino/commit/f88e5aa49cf2804d7c2df22ef1640eb4ec43dd56
github_pr

fix: escape fallback raw-content text nodes

Fix merged in angular/domino PR #32 on 2026-07-07 — awaiting tagged release

https://github.com/angular/domino/pull/32
github_pr Patch Available

[Backport 20.3.X] fix(platform-server): update domino to latest version

Patch available: angular/angular v20.3.27 (PR #69930 merged 2026-07-29)

https://github.com/angular/angular/pull/69930
github_pr Patch Available

[Backport 21.2.X] fix(platform-server): update domino to latest version

Patch available: angular/angular v21.2.19 (PR #69929 merged 2026-07-29)

https://github.com/angular/angular/pull/69929
github_pr Patch Available

Pr takeover 69411

Patch available: angular/angular v22.0.7 (PR #69714 merged 2026-07-09)

https://github.com/angular/angular/pull/69714
github_pr Patch Available

Pr takeover 69522

Patch available: angular/angular v22.1.0-next.6 (PR #69675 merged 2026-07-09)

https://github.com/angular/angular/pull/69675
github Patch Available

Missing Fallback Raw-Content Serialization Escaping leads to Cross-Site Scripting (XSS) in Angular SSR · Advisory · angular/angular · GitHub

https://github.com/angular/angular/security/advisories/GHSA-vpx6-8pjr-4g3v

Vendor Advisories for CVE-2026-69149(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
angular.js1.8.2-2, 1.8.3-1, 1.8.3-2, 1.8.3-3——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
angular.js1.8.3-1, 1.8.3-1+deb12u1, 1.8.3-1+deb12u1~deb11u1, 1.8.3-2, 1.8.3-3——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
angular.js1.8.3-3——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
angular.js1.8.3-3——
npm(1)
PackageVulnerable rangeFixed inDependents
@angular/platform-server—20.3.27—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 10:12 UTCEG score recompute
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-19 08:16 UTCEG score recompute
  5. 2026-08-18 13:49 UTCEPSS rescore
  6. 2026-08-18 13:49 UTCEPSS rescore
  7. 2026-08-18 06:19 UTCEG score recompute
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 04:23 UTCEG score recompute
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 02:26 UTCEG score recompute
  13. 2026-08-16 02:15 UTCEPSS rescore
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-13 22:33 UTCEG score recompute
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-12 20:36 UTCEG score recompute
  18. 2026-08-12 13:51 UTCEPSS rescore
  19. 2026-08-11 18:40 UTCEG score recompute▼ 2.50
  20. 2026-08-11 18:36 UTCNVD updateCVSS v3 → 6.1 · severity → MEDIUM
  21. 2026-08-11 17:53 UTCEG score recompute
  22. 2026-08-11 06:06 UTCEG score recompute
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-09 18:44 UTCEG score recompute
  25. 2026-08-09 13:47 UTCEPSS rescore
Show 15 more
  1. 2026-08-08 19:11 UTCEG score recompute
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-07 19:38 UTCEG score recompute
  4. 2026-08-06 20:05 UTCEG score recompute
  5. 2026-08-06 13:47 UTCEPSS rescore
  6. 2026-08-05 20:31 UTCEG score recompute
  7. 2026-08-05 19:17 UTCEPSS rescore
  8. 2026-08-05 19:17 UTCEPSS rescore
  9. 2026-08-04 20:58 UTCEG score recompute
  10. 2026-08-04 15:10 UTCEPSS rescore
  11. 2026-08-03 21:20 UTCEG score recompute
  12. 2026-08-03 20:43 UTCEG score recompute
  13. 2026-08-03 17:38 UTCEG score recompute
  14. 2026-08-03 16:19 UTCEG score recompute
  15. 2026-08-03 16:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-69149?
CVE-2026-69149 is a medium vulnerability published on August 3, 2026. 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…
When was CVE-2026-69149 disclosed?
CVE-2026-69149 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69149 actively exploited?
CVE-2026-69149 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.4% of all scored CVEs.
What is the CVSS score of CVE-2026-69149?
CVE-2026-69149 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-69149?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69149, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69149

Explore →

Is Your Infrastructure Affected by CVE-2026-69149?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs