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.3%, top 76% 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.3%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1MEDIUMmedium confidence
EG Risk
32
EG Risk 32/100

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%
Automatability30% × 15%
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

Published

June 15, 2026

Last Modified

July 9, 2026

Advisory Details (3)

Auto-updated Jun 22, 2026
Patch available. Sources: github_commit, github_pr, github.
githubMentions a patch (unverified)

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.2-2, 1.8.3-1, 1.8.3-2, 1.8.3-3
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.3-1, 1.8.3-1+deb12u1, 1.8.3-1+deb12u1~deb11u1, 1.8.3-2, 1.8.3-3
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.3-3
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.3-3
  • every version on: no fix on record
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@angular/core—
  • 22.0.0-next.0 up to 22.0.1: fixed in 22.0.1
  • 21.0.0-next.0 up to 21.2.17: fixed in 21.2.17
  • 20.0.0-next.0 up to 20.3.25: fixed in 20.3.25
  • every version through 19.2.25: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 26× 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.

Showing the most recent 100 of 138 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-03 07:39 UTCOSV refresh
  9. 2026-10-02 17:56 UTCEPSS rescore
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-29 15:22 UTCEPSS rescore
  13. 2026-09-28 13:51 UTCEPSS rescore
  14. 2026-09-27 13:48 UTCEPSS rescore
  15. 2026-09-26 15:59 UTCEPSS rescore
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-20 20:16 UTCEPSS rescore
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-17 19:31 UTCEPSS rescore
  21. 2026-09-16 14:08 UTCEPSS rescore
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-14 03:47 UTCEG score recompute
  24. 2026-09-13 16:47 UTCEPSS rescore
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 75 more
  1. 2026-09-10 09:35 UTCEPSS rescore
  2. 2026-09-08 22:01 UTCEPSS rescore
  3. 2026-09-06 13:47 UTCEPSS rescore
  4. 2026-09-04 05:06 UTCEPSS rescore
  5. 2026-09-02 14:12 UTCEPSS rescore
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-08-30 22:59 UTCEG score recompute
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 01:22 UTCEPSS rescore
  11. 2026-08-28 21:41 UTCEPSS rescore
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-24 23:38 UTCEG score recompute
  16. 2026-08-23 09:49 UTCEG score recompute
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-20 11:07 UTCEG score recompute
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-19 13:15 UTCEG score recompute
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-16 22:29 UTCEG score recompute
  25. 2026-08-16 14:56 UTCEPSS rescore
  26. 2026-08-16 02:14 UTCEPSS rescore
  27. 2026-08-15 02:15 UTCEG score recompute
  28. 2026-08-15 01:30 UTCEPSS rescore
  29. 2026-08-14 04:25 UTCEG score recompute
  30. 2026-08-13 22:00 UTCEPSS rescore
  31. 2026-08-13 06:34 UTCEG score recompute
  32. 2026-08-12 13:51 UTCEPSS rescore
  33. 2026-08-12 08:43 UTCEG score recompute
  34. 2026-08-11 10:51 UTCEG score recompute
  35. 2026-08-11 00:00 UTCEPSS rescore
  36. 2026-08-09 15:09 UTCEG score recompute
  37. 2026-08-09 13:46 UTCEPSS rescore
  38. 2026-08-07 19:28 UTCEG score recompute
  39. 2026-08-06 21:37 UTCEG score recompute
  40. 2026-08-06 13:47 UTCEPSS rescore
  41. 2026-08-05 23:45 UTCEG score recompute
  42. 2026-08-05 19:17 UTCEPSS rescore
  43. 2026-08-05 01:55 UTCEG score recompute
  44. 2026-08-04 15:10 UTCEPSS rescore
  45. 2026-08-04 10:39 UTCEPSS rescore
  46. 2026-08-04 02:26 UTCEG score recompute
  47. 2026-08-03 10:36 UTCEPSS rescore
  48. 2026-08-02 06:44 UTCEG score recompute
  49. 2026-08-02 02:27 UTCEPSS rescore
  50. 2026-08-01 08:53 UTCEG score recompute
  51. 2026-08-01 04:16 UTCEPSS rescore
  52. 2026-07-31 04:31 UTCEG score recompute
  53. 2026-07-30 16:28 UTCEPSS rescore
  54. 2026-07-30 05:13 UTCEG score recompute
  55. 2026-07-30 01:30 UTCEPSS rescore
  56. 2026-07-29 03:38 UTCEG score recompute
  57. 2026-07-28 15:37 UTCEPSS rescore
  58. 2026-07-27 18:18 UTCEG score recompute
  59. 2026-07-26 20:13 UTCEG score recompute
  60. 2026-07-26 14:54 UTCEPSS rescore
  61. 2026-07-25 14:18 UTCEPSS rescore
  62. 2026-07-24 14:18 UTCEPSS rescore
  63. 2026-07-23 14:18 UTCEPSS rescore
  64. 2026-07-23 03:19 UTCEG score recompute
  65. 2026-07-22 14:08 UTCEPSS rescore
  66. 2026-07-21 15:25 UTCEPSS rescore
  67. 2026-07-20 17:08 UTCEPSS rescore
  68. 2026-07-19 14:31 UTCEPSS rescore
  69. 2026-07-19 14:31 UTCEPSS rescore
  70. 2026-07-19 02:29 UTCEPSS rescore
  71. 2026-07-18 10:04 UTCEPSS rescore
  72. 2026-07-16 17:03 UTCEPSS rescore
  73. 2026-07-15 16:57 UTCEPSS rescore
  74. 2026-07-15 16:57 UTCEPSS rescore
  75. 2026-07-15 02:00 UTCEPSS rescore

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 on June 15, 2026, with the most recent update on July 9, 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 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
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?
A fix for CVE-2026-54267 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54267 are linked in the Vendor Advisories panel on this page.

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.