Angular HttpTransferCache Flaw Enables Cross-Request State Poisoning
Vulnerability Disclosure · 7 sources · Updated 4mo ago · First seen Aug 3, 2026

A high-severity vulnerability in Angular's @angular/common/http package allows semantically different HttpClient requests to collide on the same HttpTransferCache key during Server-Side Rendering and client-side hydration, enabling cross-request response reuse and client-side state poisoning. The flaw, tracked as CVE-2026-68945, stems from ambiguous query-parameter serialization in cache-key generation, including cases where repeated parameters are comma-joined or attacker-controlled delimiters such as & and = produce identical serialized forms.
The issue is remotely exploitable without authentication and carries a CVSS 4.0 score of 8.8. Angular fixed the bug by replacing custom serialization logic with native URLSearchParams sorting and encoding, and released patched versions 20.3.27, 21.2.19, and 22.0.2; versions prior to those releases are affected. Public references include Angular commits, a pull request, and a GitHub security advisory documenting the remediation.


