Response-cache poisoning via clobbered state element
Published Jun 22, 2026 · Updated Jun 22, 2026
DOM clobbering in affected Angular releases allows remote attackers to poison client hydration state through a forged element ID. The TransferState restore path trusts document.getElementById(appId + '-state') without confirming that the returned node is a script, then parses its text as JSON. Exploitation requires SSR hydration and attacker-controlled IDs rendered before the genuine state script; forged cache entries replace genuine API responses, while script execution additionally requires unsafe rendering.
Summary
What happened
DOM clobbering in affected Angular releases allows remote attackers to poison client hydration state through a forged element ID. The TransferState restore path trusts document.getElementById(appId + '-state') without confirming that the returned node is a script, then parses its text as JSON. Exploitation requires SSR hydration and attacker-controlled IDs rendered before the genuine state script; forged cache entries replace genuine API responses, while script execution additionally requires unsafe rendering.
The record
- CVE
- CVE-2026-54267
- Published
- Jun 22, 2026
- Updated
- Jun 22, 2026
- Vendor
- Go standard library
- Product
- Angular
- Classifications
- CWE-471, CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 22, 2026CVE publishedPublication date reported by the CVE source.
- Jun 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 19.2.25
- Affected versionversion=>= 20.0.0-next.0 < 20.3.25
- Affected versionversion=>= 21.0.0-next.0 < 21.2.17
- Affected versionversion=>= 22.0.0-next.0 < 22.0.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo