CVE intelligence and bounded remediation
CVE-2026-54267 — Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages
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. An…
- Severity
- High
- CVSS
- 8.6 (4.0)
- Published
- 2026-06-22
- CISA KEV
- Not currently listed
- Ecosystem
- javascript/npm
- Weaknesses
- CWE-79, CWE-471
Affected products
- angular / angular
Matched remediation archetype
Cross-site scripting and unsafe browser output
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Trace reflected, stored, and DOM-derived untrusted values into HTML, attributes, URLs, styles, scripts, and client-side template sinks.
- Identify affected origins, authenticated user roles, sensitive browser capabilities, and where content is shared across tenants.
- Review framework escaping, rich-text sanitization, legacy templates, and client-side rendering paths.
Remediate safely
- Use context-aware framework output encoding and safe DOM APIs; keep untrusted data out of executable contexts.
- Sanitize intentionally supported markup with a maintained allowlist policy and validate URLs and attributes separately.
- Update affected rendering components and add tests for every output context using inert sentinel markup.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.