Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilitywidely-deployed-product-advisoryinternet-facing-service-vulnerabilityproof-of-concept-release

Angular HttpTransferCache Flaw Enables Cross-Request State Poisoning

Vulnerability Disclosure · 7 sources · Updated 4mo ago · First seen Aug 3, 2026

Angular HttpTransferCache Flaw Enables Cross-Request State Poisoning

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.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

3 events · Jun 11, 2026 – Aug 3, 2026
  1. Aug 3, 20264mo ago

    CVE-2026-68945 is published for Angular HttpTransferCache flaw

    CVE-2026-68945 was published as a high-severity vulnerability affecting Angular's HttpTransferCache in @angular/common. The flaw allows semantically different requests to collide on the same cache key, enabling cross-request response reuse and client-side state poisoning.

    CVE-2026-68945: CVE-2026-68945: Cache-Key Ambiguity in Angular HttpTransferCache Leading to State Poisoning | CVEReports
  2. Aug 3, 20264mo ago

    Angular fixes CVE-2026-68945 in patched releases

    Angular patched the HttpTransferCache cache-key ambiguity issue in @angular/common by replacing custom parameter serialization with native URLSearchParams sorting and encoding. Fixed versions include 20.3.27, 21.2.19, and 22.0.2, and the advisory states the patches were released on the same day.

    CVE-2026-68945: CVE-2026-68945: Cache-Key Ambiguity in Angular HttpTransferCache Leading to State Poisoning | CVEReports
  3. Jun 11, 20265mo ago

    Angular commits transfer cache parameter normalization fix

    Angular committed a change to its HTTP transfer cache logic that replaced custom parameter normalization with URLSearchParams sorting and serialization, preventing cache-key collisions between comma-separated scalar values and repeated query parameters. The commit also added a regression test verifying that `role=user,admin` and `role=user&role=admin` are cached distinctly.

    fix(http): distinguish repeated transfer cache params · angular/angular@a6c7fc5 · GitHub
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

2 linked
AngularAngular

Organizations

1 linked
Angular
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.