CVE-2026-68945
HttpTransferCache key collision can return wrong backend responses
Is CVE-2026-68945 being exploited?
Not confirmed. CVE-2026-68945 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.12% probability of exploitation in the next 30 days.
How severe is CVE-2026-68945?
CVE-2026-68945 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-68945?
Yes. A fix has been recorded for CVE-2026-68945. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-68945 affect?
CVE-2026-68945 affects Angular HttpClient (HttpTransferCache), Angular <20.3.27, Angular <21.2.19, Angular <22.0.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-68945?
Upgrade to 20.3.27, 21.2.19, or 22.0.2 and audit HttpClient caching usage
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
HttpTransferCache comma-joins repeated params so distinct HttpClient requests can receive cached wrong backend responses, risking data leakage or cache poisoning.
Patch when possible
- affected< 20.3.27
- affected>= 21.0.0-next.0 and < 21.2.19
- affected>= 22.0.0-next.0 and < 22.0.2
- affected< 20.3.27
- affected>= 21.0.0-next.0 and < 21.2.19
- affected>= 22.0.0-next.0 and < 22.0.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.