CVE-2026-50170

Angular: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache

HIGH
7.5
CVSS Score
Published: June 22, 2026 at 03:39 PM UTC
Updated: July 9, 2026 at 03:31 PM UTC
1 product affected across 1 vendor@angular

Using angular by angular?

Get instant alerts when new vulnerabilities affect angular - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23, a vulnerability was discovered in @angular/common when Server-Side Rendering (SSR) and hydration are enabled. The HttpTransferCache utility optimizes hydration by caching outgoing HTTP requests performed during SSR and transferring the cached state to the client-side application via TransferState. However, the caching mechanism fails to inspect the withCredentials flag or the Cookie header of outgoing requests. As a result, credentialed, user-specific responses may be cached by default in the shared TransferState payload. When these responses are serialized into the HTML, any caching layer (such as a CDN, reverse proxy, or shared server cache) that caches the SSR-rendered HTML page could inadvertently cache and leak one user's private data to other users, leading to a high-severity information disclosure vulnerability. This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≤ 18.2.14v < 19.2.23v < 20.3.22v < 21.2.15v < 22.0.0-rc.219.0.0 ≤ v < 19.2.2320.0.0 ≤ v < 20.3.2221.0.0 ≤ v < 21.2.1522.0.0 next022.0.0 next122.0.0 next1022.0.0 next1122.0.0 next1222.0.0 next222.0.0 next322.0.0 next422.0.0 next522.0.0 next622.0.0 next722.0.0 next822.0.0 next922.0.0 rc022.0.0 rc1
Affected range stops below 19.2.23, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.3.22, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.0.0-rc.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

x_refsource_CONFIRMThird Party Advisory
Source: cverecord
https://github.com/angular/angular/security/advisories/GHSA-q6f4-qqrg-jv6x
x_refsource_MISCIssue TrackingPatch
Source: cverecord
https://github.com/angular/angular/pull/67964

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-524

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card