CVE-2026-68945: Cache-Key Ambiguity in Angular HttpTransferCache
- Vendor
- Angular
CVE-2026-68945 is a cache-key ambiguity vulnerability in Angular's HttpTransferCache, used during server-side rendering and client-side hydration. The sortAndConcatParams logic comma-joins repeated query-parameter values through implicit array-to-string conversion and does not percent-encode parameter keys and values. Consequently, semantically distinct HttpClient requests can generate identical transfer-cache keys and incorrectly reuse backend responses. Collisions can arise between comma-containing scalar values and repeated parameters, or through embedded parameter delimiters. The issue affects @angular/common releases before the applicable fixes in 20.3.27, 21.2.19, and 22.0.2 and can cause response confusion and application-state poisoning.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can cause a security-sensitive HttpClient request to receive a cached response belonging to a semantically different request. This can poison server-rendered output and client-side state during hydration, potentially exposing sensitive response data or corrupting displayed content, authorization-related state, or user context. The concrete consequences depend on how the application uses the affected responses; an authorization bypass is not established for every affected application. The assigned CVSS v4.0 score is 8.8, reflecting high confidentiality impact, low integrity impact, and no availability impact.
Mitigation
If you can’t patch tonight, do this now.
Until an upgrade is possible, exclude sensitive HttpClient requests that use repeated parameter keys from transfer caching by setting transferCache: false. Alternatively, disable HTTP transfer caching globally with withNoHttpTransferCache() in the application bootstrap configuration.
Remediation
Patch, then assume compromise.
Upgrade Angular, including @angular/common, to 20.3.27, 21.2.19, or 22.0.2 for the corresponding release line, or a later patched release. The fix replaces custom parameter concatenation with URLSearchParams sorting and serialization, preserving distinctions between repeated parameters and comma-containing values while percent-encoding delimiters. For SQL Assistant for VMware Tanzu Data Intelligence deployments, upgrade to release 1.0.4, which includes this security fix; verify the intended replacement version against the release documentation because the advisory's component table contains a version discrepancy.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-68945 exploited in the wild?
- As of Oct 23, 2026, Mallory has no reports of CVE-2026-68945 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-68945?
- As of Oct 23, 2026, Mallory has found no public exploit for CVE-2026-68945.
- Is there a patch for CVE-2026-68945?
- Upgrade Angular, including @angular/common, to 20.3.27, 21.2.19, or 22.0.2 for the corresponding release line, or a later patched release. The fix replaces custom parameter concatenation with URLSearchParams sorting and serialization, preserving distinctions between repeated parameters and comma-containing values while percent-encoding delimiters.
- What products are affected by CVE-2026-68945?
- Angular.
- How severe is CVE-2026-68945?
- CVE-2026-68945 has a CVSS v4 score of 8.8 (High) and an EPSS score of 0.18% (7th percentile) as of Oct 23, 2026.
Recent activity
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.