CVE-2026-54266 Details
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, Angular's HttpTransferCache caches HTTP requests made during Server-Side Rendering (SSR) so that they can be reused during client-side hydration. This avoids repeating the same HTTP requests on the client. The cached responses are stored in TransferState using a cache key generated by hashing request properties (method, response type, mapped URL, serialized body, and sorted query parameters). The cache keys are generated using a weak 32-bit DJB2-like polynomial rolling hash. The 32-bit hash space is extremely small, allowing attackers to find hash collisions. An attacker can easily find a query parameter string (e.g., q=aaCAZMMM for a search request) that produces the exact same 32-bit hash as a sensitive endpoint (e.g., /api/user/profile). When a victim visits a crafted link containing the colliding parameter, the SSR process executes both the search request and the profile request. Due to the hash collision, the search response overwrites the profile response in the TransferState cache. This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25.
A vulnerability exists in Angular's HttpTransferCache component, which caches HTTP requests during Server-Side Rendering (SSR) for reuse during client-side hydration. This caching mechanism is intended to prevent redundant HTTP requests on the client. However, prior to versions 22.0.1, 21.2.17, and 20.3.25, the cache key generation relied on a weak 32-bit DJB2-like polynomial rolling hash, creating a small hash space susceptible to collisions. An attacker could exploit this by crafting a query parameter that collides with a hash from a sensitive endpoint, leading to the overwriting of critical response data in the TransferState cache. When the application later retrieves this data, it inadvertently serves the attacker's manipulated response instead of the genuine one, potentially causing state poisoning or unauthorized information disclosure.
Upgrade to Angular versions 22.0.1, 21.2.17, or 20.3.25. If an immediate upgrade is not possible, configure HttpClient requests to skip transfer caching for sensitive endpoints or disable the HTTP transfer cache globally in the application bootstrap configuration.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 22, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/angular/angular/commit/5f36274da3f961430ae72865159afa02a1dd9133 | [email protected] | Patch |
| https://github.com/angular/angular/pull/69153 | [email protected] | Issue TrackingPatch |
| https://github.com/angular/angular/security/advisories/GHSA-39pv-4j6c-2g6v | [email protected] | Third Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-328 | Use of Weak Hash | [email protected] |
| CWE-345 | Insufficient Verification of Data Authenticity | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| angular angular | <= 19.2.25 >= 20.0.0, < 20.3.25 >= 21.0.0, < 21.2.17 >= 22.0.0, < 22.0.1 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 9, 2026 | Reanalysis | [email protected] |
| Jun 26, 2026 | Initial Analysis | [email protected] |
| Jun 22, 2026 | CVE Modified | CISA-ADP |
| Jun 22, 2026 | New CVE Received | [email protected] |