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.
CVE-2026-50170
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 18.4%
- KEV
- Not listed
Published
June 15, 2026
Last Modified
June 30, 2026
Advisory Details (2)
Auto-updated Jun 22, 2026Information Leak via Default Caching of Credentialed Requests in HttpTransferCache · Advisory · angular/angular · GitHub
https://github.com/angular/angular/security/advisories/GHSA-q6f4-qqrg-jv6xfix(http): skip TransferCache for cookie-bearing requests by default
Fix merged in angular/angular PR #67964 on 2026-05-27 — awaiting tagged release
https://github.com/angular/angular/pull/67964Vendor Advisories for CVE-2026-50170(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @angular/common | — | 21.2.15 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 46× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 00:23 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 22:54 UTCEG score recompute
- 2026-07-05 10:40 UTCEG score recompute
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 22:20 UTCEG score recompute
- 2026-07-04 10:04 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 15:22 UTCEG score recompute
- 2026-07-03 03:01 UTCEG score recompute
- 2026-07-02 14:47 UTCEG score recompute
- 2026-07-02 02:32 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 14:19 UTCEG score recompute
- 2026-07-01 02:05 UTCEG score recompute▼ 0.70
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 14:32 UTCNVD updateCVSS v3 → 7.5
- 2026-06-30 13:50 UTCEG score recompute
- 2026-06-30 01:36 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 13:22 UTCEG score recompute
- 2026-06-29 01:08 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
Show 21 moreShow fewer
- 2026-06-28 12:54 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 00:41 UTCEG score recompute
- 2026-06-27 12:26 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-27 00:12 UTCEG score recompute
- 2026-06-26 11:58 UTCEG score recompute
- 2026-06-25 21:19 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 09:05 UTCEG score recompute
- 2026-06-24 20:52 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 08:38 UTCEG score recompute
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 20:24 UTCEG score recompute
- 2026-06-23 08:07 UTCEG score recompute
- 2026-06-22 19:43 UTCEG score recompute▲ 8.20
- 2026-06-22 19:40 UTCNVD updateCVSS v3 → 8.2 · CVSS v4 → 8.2
- 2026-06-15 17:16 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-50170?
When was CVE-2026-50170 disclosed?
Is CVE-2026-50170 actively exploited?
What is the CVSS score of CVE-2026-50170?
How do I remediate CVE-2026-50170?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50170
Is Your Infrastructure Affected by CVE-2026-50170?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.