CVE-2026-54267

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 92% 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.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: NoneExposed: 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 22.0.1, 21.2.17, and 20.3.25, to optimize client-side bootstrap in Server-Side Rendered (SSR) environments, Angular supports Hydration via provideClientHydration(). During SSR, Angular serializes the application's runtime state (such as cached HttpClient responses) and outputs it into the HTML stream as a tag with a predictable identifier. During client bootstrap, Angular recovers this state by looking up the element via document.getElementById('ng-state') and parsing its text content. Because the DOM element lookup for the state container is predictable and relies solely on the ID selector (ng-state), it is susceptible to DOM Clobbering. If the application binds untrusted user input or CMS content to element properties such as id (e.g., or ) before the genuine tag is parsed by the browser, the attacker-controlled element takes precedence in the DOM lookup. During hydration, when Angular calls document.getElementById('ng-state'), the browser returns the attacker's clobbered element. Angular then attempts to parse the text content or attributes of this clobbered element as JSON. This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25.

CVSS v3
6.1
EG Score
6.1(medium)
EPSS
7.6%
KEV
Not listed

Published

June 15, 2026

Last Modified

June 26, 2026

Advisory Details (3)

Auto-updated Jun 22, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

Angular Client Hydration DOM Clobbering & Response-Cache Poisoning · Advisory · angular/angular · GitHub

https://github.com/angular/angular/security/advisories/GHSA-rgjc-h3x7-9mwg
github_pr Patch Available

fix(core): harden TransferState restoration against DOM clobbering

Patch available: angular/angular v22.1.0-next.0 (PR #69064 merged 2026-06-03)

https://github.com/angular/angular/pull/69064
github_commit Patch Available

commit 6bde84fa8e6a (angular/angular)

Patch available: angular/angular v22.1.0-next.0 (contains commit 6bde84fa8e6a)

https://github.com/angular/angular/commit/6bde84fa8e6a5770b54040fbbc9bf10d5d0386fa

Vendor Advisories for CVE-2026-54267(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@angular/core

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 42× 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-07-07 00:24 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 09:26 UTCEG score recompute
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 10:05 UTCEG score recompute
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 10:02 UTCEG score recompute
  13. 2026-07-02 12:10 UTCEG score recompute
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-07-01 14:17 UTCEG score recompute
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 16:25 UTCEG score recompute
  18. 2026-06-29 18:34 UTCEG score recompute
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-28 19:40 UTCEG score recompute
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 21:49 UTCEG score recompute
Show 17 more
  1. 2026-06-27 03:08 UTCEPSS rescore
  2. 2026-06-26 23:57 UTCEG score recompute 2.50
  3. 2026-06-26 19:41 UTCNVD updateCVSS v3 → 6.1 · severity → MEDIUM
  4. 2026-06-26 11:58 UTCEG score recompute
  5. 2026-06-25 20:27 UTCEG score recompute
  6. 2026-06-25 13:49 UTCEPSS rescore
  7. 2026-06-25 08:28 UTCEG score recompute
  8. 2026-06-24 20:27 UTCEG score recompute
  9. 2026-06-24 14:05 UTCEPSS rescore
  10. 2026-06-24 06:43 UTCEG score recompute
  11. 2026-06-23 21:33 UTCEPSS rescore
  12. 2026-06-23 21:33 UTCEPSS rescore
  13. 2026-06-23 18:24 UTCEG score recompute
  14. 2026-06-23 06:23 UTCEG score recompute
  15. 2026-06-22 17:52 UTCEG score recompute 8.60
  16. 2026-06-22 17:45 UTCNVD updateCVSS v3 → 8.6 · CVSS v4 → 8.6
  17. 2026-06-15 16:14 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54267?
CVE-2026-54267 is a medium vulnerability published on June 15, 2026. Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.1, 21.2.17, and 20.3.25, to optimize client-side bootstrap in Server-Side Rendered (SSR) environments, Angular supports Hydration via…
When was CVE-2026-54267 disclosed?
CVE-2026-54267 was first published in the National Vulnerability Database on June 15, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54267 actively exploited?
CVE-2026-54267 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54267?
CVE-2026-54267 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-54267?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54267, 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-54267

Explore →

Is Your Infrastructure Affected by CVE-2026-54267?

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