CVE-2026-68945 is a high-severity vulnerability in Angular's HttpTransferCache implementation in the @angular/common HTTP stack used during server-side rendering and client hydration. In affected versions, repeated query parameters are serialized by comma-joining values when constructing the transfer-cache key. This ambiguous serialization causes semantically distinct HttpClient requests to generate the same cache key. As a result, a cached backend response for one request can be incorrectly reused for a different request during hydration. The flaw stems from improper query-parameter serialization logic that failed to preserve the distinction between repeated parameters and comma-containing scalar values, and did not safely encode delimiter characters. Fixed releases replace the custom serialization behavior with native URLSearchParams sorting and serialization to ensure distinct requests produce distinct cache keys.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A cache-key ambiguity flaw in Angular HttpTransferCache that can cause semantically distinct HttpClient requests to collide on the same transfer-cache key, leading to cross-request response reuse and state poisoning.
A high-severity cache-key ambiguity vulnerability in Angular's @angular/common/http HttpTransferCache during SSR hydration that can cause cross-request response reuse and client-side state poisoning.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.