Common: Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning (CVE-2026-68945)
Angular's HttpTransferCache used during Server-Side Rendering (SSR) improperly generates identical cache keys for distinct HTTP requests when repeated query parameter keys are present. This cache-key ambiguity can cause responses from one request to be reused for semantically different requests within the same render, leading to state poisoning and cross-request response reuse. Patched versions 20.3.27, 21.2.19, and 22.0.2 address this issue. Workarounds include disabling transfer caching on sensitive requests or globally disabling the HTTP transfer cache.
AI Analysis
Technical Summary
The vulnerability in Angular's HttpTransferCache arises because it serializes repeated HTTP query parameters by joining their values with commas, causing distinct requests with repeated keys to produce identical cache keys. This allows a cached response from one request to be incorrectly reused for another request with different parameters during SSR hydration. The impact includes state poisoning and cross-request response reuse, where attacker-influenced cached responses can affect trusted requests. The issue affects Angular versions up to and including 19.2.25 and is fixed in versions 20.3.27, 21.2.19, and 22.0.2.
Potential Impact
An attacker can cause Angular server-rendered output to be based on incorrect backend responses by exploiting the cache-key ambiguity, leading to state poisoning and cross-request response reuse. This can result in security-sensitive requests receiving attacker-influenced cached responses instead of fresh backend data, potentially compromising application logic and data integrity.
Mitigation Recommendations
A fix is available in Angular versions 20.3.27, 21.2.19, and 22.0.2. Users should upgrade to one of these patched versions to resolve the vulnerability. If immediate upgrade is not possible, configure HttpClient requests to disable transfer caching on sensitive endpoints by setting 'transferCache: false'. Alternatively, disable the HTTP transfer cache globally in the application bootstrap configuration using 'withNoHttpTransferCache()'.
Common: Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning (CVE-2026-68945)
Description
Angular's HttpTransferCache used during Server-Side Rendering (SSR) improperly generates identical cache keys for distinct HTTP requests when repeated query parameter keys are present. This cache-key ambiguity can cause responses from one request to be reused for semantically different requests within the same render, leading to state poisoning and cross-request response reuse. Patched versions 20.3.27, 21.2.19, and 22.0.2 address this issue. Workarounds include disabling transfer caching on sensitive requests or globally disabling the HTTP transfer cache.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Angular's HttpTransferCache arises because it serializes repeated HTTP query parameters by joining their values with commas, causing distinct requests with repeated keys to produce identical cache keys. This allows a cached response from one request to be incorrectly reused for another request with different parameters during SSR hydration. The impact includes state poisoning and cross-request response reuse, where attacker-influenced cached responses can affect trusted requests. The issue affects Angular versions up to and including 19.2.25 and is fixed in versions 20.3.27, 21.2.19, and 22.0.2.
Potential Impact
An attacker can cause Angular server-rendered output to be based on incorrect backend responses by exploiting the cache-key ambiguity, leading to state poisoning and cross-request response reuse. This can result in security-sensitive requests receiving attacker-influenced cached responses instead of fresh backend data, potentially compromising application logic and data integrity.
Mitigation Recommendations
A fix is available in Angular versions 20.3.27, 21.2.19, and 22.0.2. Users should upgrade to one of these patched versions to resolve the vulnerability. If immediate upgrade is not possible, configure HttpClient requests to disable transfer caching on sensitive endpoints by setting 'transferCache: false'. Alternatively, disable the HTTP transfer cache globally in the application bootstrap configuration using 'withNoHttpTransferCache()'.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-jhpw-976m-542j
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-68945"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a710665bf32cb7a34394b64
Added to database: 08/03/2026, 21:21:41 UTC
Last enriched: 08/03/2026, 21:32:10 UTC
Last updated: 08/03/2026, 23:46:35 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.