CVE-2026-50170

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 64% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

Published

June 15, 2026

Last Modified

July 9, 2026

Advisory Details (2)

Auto-updated Jun 22, 2026
Patch available. Sources: github_pr, github.
githubMentions a patch (unverified)

Information Leak via Default Caching of Credentialed Requests in HttpTransferCache · Advisory · angular/angular · GitHub

https://github.com/angular/angular/security/advisories/GHSA-q6f4-qqrg-jv6x
github_pr

fix(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/67964

Vendor 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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.2-2, 1.8.3-1, 1.8.3-2, 1.8.3-3
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.3-1, 1.8.3-1+deb12u1, 1.8.3-1+deb12u1~deb11u1, 1.8.3-2, 1.8.3-3
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.3-3
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.3-3
  • every version on: no fix on record
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@angular/common—
  • 22.0.0-next.0 up to 22.0.0-rc.2: fixed in 22.0.0-rc.2
  • 20.0.0-next.0 up to 20.3.22: fixed in 20.3.22
  • 19.0.0-next.0 up to 19.2.23: fixed in 19.2.23
  • every version through 18.2.14: no fix on record
  • 21.0.0-next.0 up to 21.2.15: fixed in 21.2.15
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 24× 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.

Showing the most recent 100 of 134 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-03 07:39 UTCOSV refresh
  9. 2026-10-02 17:56 UTCEPSS rescore
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-26 00:27 UTCEPSS rescore
  16. 2026-09-23 17:53 UTCEPSS rescore
  17. 2026-09-20 20:16 UTCEPSS rescore
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-14 03:46 UTCEG score recompute
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-10 09:35 UTCEPSS rescore
  25. 2026-09-08 22:01 UTCEPSS rescore
Show 75 more
  1. 2026-09-07 16:01 UTCEPSS rescore
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-09-01 04:40 UTCEPSS rescore
  7. 2026-08-30 22:59 UTCEG score recompute
  8. 2026-08-30 19:17 UTCEPSS rescore
  9. 2026-08-30 01:22 UTCEPSS rescore
  10. 2026-08-28 21:41 UTCEPSS rescore
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-26 14:46 UTCEPSS rescore
  13. 2026-08-25 13:49 UTCEPSS rescore
  14. 2026-08-24 23:34 UTCEG score recompute
  15. 2026-08-23 09:48 UTCEG score recompute
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-21 09:53 UTCEG score recompute
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 08:41 UTCEG score recompute
  21. 2026-08-19 17:04 UTCEPSS rescore
  22. 2026-08-19 13:15 UTCEG score recompute
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 00:49 UTCEG score recompute
  26. 2026-08-16 14:56 UTCEPSS rescore
  27. 2026-08-16 12:35 UTCEG score recompute
  28. 2026-08-16 02:14 UTCEPSS rescore
  29. 2026-08-15 12:05 UTCEG score recompute
  30. 2026-08-15 01:30 UTCEPSS rescore
  31. 2026-08-13 23:25 UTCEG score recompute
  32. 2026-08-13 22:00 UTCEPSS rescore
  33. 2026-08-12 22:53 UTCEG score recompute
  34. 2026-08-12 13:51 UTCEPSS rescore
  35. 2026-08-11 22:26 UTCEG score recompute
  36. 2026-08-11 10:13 UTCEG score recompute
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-09 21:32 UTCEG score recompute
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-08 21:06 UTCEG score recompute
  41. 2026-08-08 16:37 UTCEPSS rescore
  42. 2026-08-07 20:39 UTCEG score recompute
  43. 2026-08-06 20:12 UTCEG score recompute
  44. 2026-08-06 13:47 UTCEPSS rescore
  45. 2026-08-05 19:45 UTCEG score recompute
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-04 15:42 UTCEG score recompute
  48. 2026-08-04 15:10 UTCEPSS rescore
  49. 2026-08-04 10:39 UTCEPSS rescore
  50. 2026-08-03 22:12 UTCEG score recompute
  51. 2026-08-03 10:36 UTCEPSS rescore
  52. 2026-08-01 08:53 UTCEG score recompute
  53. 2026-08-01 04:16 UTCEPSS rescore
  54. 2026-07-30 23:55 UTCEG score recompute
  55. 2026-07-30 16:28 UTCEPSS rescore
  56. 2026-07-30 05:12 UTCEG score recompute
  57. 2026-07-30 01:30 UTCEPSS rescore
  58. 2026-07-29 03:27 UTCEG score recompute
  59. 2026-07-28 15:37 UTCEPSS rescore
  60. 2026-07-28 01:54 UTCEG score recompute
  61. 2026-07-26 20:13 UTCEG score recompute
  62. 2026-07-26 14:54 UTCEPSS rescore
  63. 2026-07-25 14:18 UTCEPSS rescore
  64. 2026-07-24 14:18 UTCEPSS rescore
  65. 2026-07-23 14:18 UTCEPSS rescore
  66. 2026-07-23 03:18 UTCEG score recompute
  67. 2026-07-22 14:08 UTCEPSS rescore
  68. 2026-07-20 17:08 UTCEPSS rescore
  69. 2026-07-19 14:31 UTCEPSS rescore
  70. 2026-07-19 14:31 UTCEPSS rescore
  71. 2026-07-19 02:29 UTCEPSS rescore
  72. 2026-07-18 10:04 UTCEPSS rescore
  73. 2026-07-16 17:03 UTCEPSS rescore
  74. 2026-07-15 16:57 UTCEPSS rescore
  75. 2026-07-15 16:57 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-50170?
CVE-2026-50170 is a high vulnerability published on June 15, 2026. 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…
When was CVE-2026-50170 disclosed?
CVE-2026-50170 was first published on June 15, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50170 actively exploited?
CVE-2026-50170 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50170?
CVE-2026-50170 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-50170?
A fix for CVE-2026-50170 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50170 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50170

Explore →

Is Your Infrastructure Affected by CVE-2026-50170?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs