CVE-2026-54267: Angular Client Hydration DOM Clobbering & Response-Cache Poisoning
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…
Published Jun 15, 2026 · Updated Jul 15, 2026
Affected packages
@angular/core
- Ecosystem
- npm
- Affected
- >= 22.0.0-next.0, < 22.0.1
- Fixed in
- 22.0.1
- Check
npm ls @angular/core
@angular/core
- Ecosystem
- npm
- Affected
- >= 21.0.0-next.0, < 21.2.17
- Fixed in
- 21.2.17
- Check
npm ls @angular/core
@angular/core
- Ecosystem
- npm
- Affected
- >= 20.0.0-next.0, < 20.3.25
- Fixed in
- 20.3.25
- Check
npm ls @angular/core
@angular/core
- Ecosystem
- npm
- Affected
- <= 19.2.25
- Fixed in
- No patched version yet
- Check
npm ls @angular/core
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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:
<script type="application/json" id="ng-state">
{"some-api-url": {"body": ...}}
</script>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.
Impact
By clobbering the state element, the attacker can inject a custom JSON payload into Angular's TransferState cache. The most critical exploitation vector is poisoning the HTTP Transfer Cache.
- The attacker injects a clobbered
ng-stateelement containing custom JSON. - The JSON maps a key (representing a target API endpoint URL) to a malicious payload of the attacker's choice.
- During client-side initialization, Angular's
HttpClientchecksTransferStatebefore making requests. Finding the poisoned key,HttpClientreturns the forged response instantly instead of requesting the genuine backend API.
Depending on how the application processes and renders the affected API response, this can lead to:
- DOM-based Cross-Site Scripting (XSS) if poisoned fields are rendered using unsafe bindings.
- Privilege Escalation by spoofing user info or session details retrieved from poisoned API payloads.
- UI Hijacking and redirection by spoofing configuration endpoints.
Patched Versions
- 22.0.1
- 21.2.17
- 20.3.25
Workarounds
If you cannot immediately update to a patched Angular version, apply the following workarounds:
A. Avoid Dynamic/User-Controlled IDs
Avoid binding raw user-supplied values or dynamic CMS IDs directly to element attributes. If dynamic IDs are required, sanitize them or prepend a static safe prefix:
<!-- Vulnerable Pattern -->
...
<!-- Mitigated Pattern -->
...B. Configure a Custom Application ID
Declaring a unique, non-predictable APP_ID changes the ID suffix of the state element, making it harder for attackers to predict and target:
// app.config.ts
import { APP_ID } from '@angular/core';
import { provideClientHydration } from '@angular/platform-browser';
export const appConfig = {
providers: [
{ provide: APP_ID, useValue: 'unique-obfuscated-app-id' },
provideClientHydration()
]
};
This changes the state element lookup ID from ng-state to unique-obfuscated-app-id-state.
Credited to SkyZeroZx, AndrewKushnir, alan-agius4, josephperrott, JeanMeche.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-88057
Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler
medium5.3No fixSep 10, 2026CVE-2026-69151
Angular i18n: Cross-Site Scripting (XSS) via event-handler attributes
high7.6No fixAug 3, 2026CVE-2026-50557
Angular: Template and Attribute Namespace Sanitization Bypass (XSS)
medium6.1No fixJun 15, 2026CVE-2026-52725
@angular/core: Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS)
medium6.1No fixJun 15, 2026CVE-2026-32635
Angular vulnerable to XSS in i18n attribute bindings
high9.0No fixMar 13, 2026CVE-2026-27970
Angular i18n vulnerable to Cross-Site Scripting
high6.1No fixFeb 27, 2026
