CVE-2026-54267

Angular Client Hydration DOM Clobbering & Response-Cache Poisoning

MEDIUM
6.1
CVSS Score
Published: June 22, 2026 at 03:30 PM UTC
Updated: July 9, 2026 at 03:39 PM UTC
1 product affected across 1 vendor@angular

Using angular by angular?

Get instant alerts when new vulnerabilities affect angular - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.1
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

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 <script> 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., <div [id]="userInput"> or <a id="ng-state">) before the genuine <script> 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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≤ 19.2.25v < 20.3.25v < 21.2.17v < 22.0.120.0.0 ≤ v < 20.3.2521.0.0 ≤ v < 21.2.1722.0.0 ≤ v < 22.0.1
Affected range stops below 20.3.25, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.0.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

x_refsource_CONFIRMThird Party Advisory
Source: cverecord
https://github.com/angular/angular/security/advisories/GHSA-rgjc-h3x7-9mwg
x_refsource_MISCIssue TrackingPatch
Source: cverecord
https://github.com/angular/angular/pull/69064

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
CHANGED
Confidentiality
LOW
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-79CWE-471

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card