Servers and applications
CVE-2026-68945
Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning
- Severity
- High 8.8
- Published
- 29 Jul 2026
- Last changed
- 3 Aug 2026
- Added to UpHeron
- 3 Nov 2026
- Exploit chance
- 0.2% in the next 30 daysHigher than 7% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read data · Change some data
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N- Also known as
- GHSA-jhpw-976m-542j
- Sources
- Project advisories (GitHub)
Description
Angular's HttpTransferCache caches HTTP requests made during Server-Side Rendering (SSR) so that they can be reused during client-side hydration.
During SSR, HttpTransferCache previously generated identical key material for distinct request parameters when repeated values were present because repeated values were joined with commas:
Both requests previously serialized as role=user,admin, allowing distinct HttpClient requests to produce the same transfer-cache key material.
In an SSR application, this cache-key ambiguity can make a later security-sensitive HttpClient request receive the response from an earlier semantically different request in the same render. For example, an attacker-influenced scalar-comma request can be cached and then replayed as the response for a trusted repeated-param authorization or data request to the same URL. As a result, Angular's server-rendered output can be based on the wrong backend response because the trusted request is not dispatched.
Workarounds
If you cannot upgrade immediately, configure your HttpClient requests to skip transfer caching for sensitive endpoints where repeated parameter keys are used:
Alternatively, disable the HTTP transfer cache globally in your application bootstrap config:
Affected software
| Software | Affected versions |
|---|---|
AngularServers and applications · github:angular/angular |
|
About Angular
web application framework
- Developers who used it in the past year
- 18.2%Stack Overflow Developer Survey 2025, 2025
- Weekly downloads (npm)
- 8,195,583npm, 15 Nov 2026
- GitHub stars
- 101,504GitHub, 15 Nov 2026
- Forks
- 28,216GitHub, 15 Nov 2026
- Latest release
- v22.2.6GitHub, 15 Nov 2026
- Released
- 12 Nov 2026GitHub
- Developer
- GoogleWikidata
- License
- MIT LicenseWikidata
- Written in
- TypeScriptWikidata
- First released
- 15 Sept 2016Wikidata
- First published on GitHub
- 18 Sept 2014GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 22 | 22.2.6 | Until 30 Jun 2028 |
| 21 | 21.2.26 | Until 30 Jun 2027 |
| 20 | 20.3.35 | Until 28 Nov 2026 |
| 19 | 19.2.25 | Ended 19 May 2026 |
| 18 | 18.2.14 | Ended 21 Nov 2025 |
| 17 | 17.3.12 | Ended 15 May 2025 |
From endoflife.date.
Vulnerabilities in Angular
- In our list
- 39
- Published in the last 12 months
- 38
- Critical, last 12 months
- 1
- High, last 12 months
- 26
- Known exploited
- 0
- GHSA-ffj9-42qx-f38hCross-Site Scripting (XSS) via AngularJS Double Compilation in @angular/upgrade's downgradeComponent()Medium 6.3 9 Nov 2026
- CVE-2026-111753XSRF Token Leakage via URL Parsing Discrepancy in Angular HTTP Client (Incomplete fix for CVE-2025-66035)Medium 5.9 16 Oct 2026
- CVE-2026-111751Denial of Service via RouterLink Query Parameter Retention in Server-Side Rendering (SSR)High 8.2 1 Oct 2026
- CVE-2026-111752Denial of Service via Unmatched Empty-Path Outlet Route Matching in Server-Side Rendering (SSR)High 8.2 30 Sept 2026
- CVE-2026-111754Open Redirect via Protocol-Relative URLs in Server-Side Rendering (SSR)Medium 5.1 30 Sept 2026
- CVE-2026-101896Denial of Service via Numeric URL Matrix Parameters in Server-Side Rendering (SSR)High 8.2 23 Sept 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-68945
- GitHub Advisory Database https://github.com/advisories/GHSA-jhpw-976m-542j
- github.com https://github.com/angular/angular/security/advisories/GHSA-jhpw-976m-542j