CVE-2026-88059

MEDIUMPre-NVD 4.04.0
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% 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, secondary
4.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.28, 21.2.20, and 22.1.1, Angular's @angular/common HttpTransferCache can cache an authenticated response when Server-Side Rendering (SSR) and hydration use a hierarchical HttpClient configured with withRequestsMadeViaParent. The child TransferCache evaluates an initially anonymous request before delegation, then a parent withInterceptors chain adds an Authorization header, cookie, or API token; although the parent cache skips the authenticated request, the child still stores the private response in TransferState serialized as JSON in the ng-state script. Exploitation requires provideClientHydration, child provideHttpClient delegation through withRequestsMadeViaParent, parent-level credential injection, and an SSR HTML response shared across users by a CDN, reverse proxy, or application cache. A later unauthenticated or unauthorized visitor can receive the cached HTML containing the earlier authenticated user's sensitive response data. Applications can mitigate by attaching credentials at the child, filtering sensitive endpoints with withHttpTransferCacheOptions, disabling transfer caching for sensitive routes, or marking personalized HTML private or no-store. This issue is fixed in versions 20.3.28, 21.2.20, and 22.1.1.

CVSS v3
4.0
EG Score
4.0(medium)
EG Risk
18(Track)
EG Risk 18/100SSVC: Track

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
Severity40% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

September 10, 2026

Last Modified

September 11, 2026

Advisory Details (9)

Auto-updated Sep 10, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
github Patch Available

Information Leak via `HttpTransferCache` Bypass When Using `withRequestsMadeViaParent` · Advisory · angular/angular · GitHub

https://github.com/angular/angular/security/advisories/GHSA-p297-fm68-3q8c
github_release Patch Available

22.1.1

Patch available: angular/angular v22.1.1

https://github.com/angular/angular/releases/tag/v22.1.1
github_release Patch Available

21.2.20

Patch available: angular/angular v21.2.20

https://github.com/angular/angular/releases/tag/v21.2.20
github_release Patch Available

20.3.28

Patch available: angular/angular v20.3.28

https://github.com/angular/angular/releases/tag/v20.3.28
github_pr Patch Available

fix(http): run root interceptors in the terminal request chain

Patch available: angular/angular v22.2.0-next.1 (PR #69778 merged 2026-07-31)

https://github.com/angular/angular/pull/69778
generic

`HttpTransferCache` can cache authenticated responses when using `withRequestsMadeViaParent` · Issue #69777 · angular/angular · GitHub

https://github.com/angular/angular/issues/69777
github_commit Patch Available

commit e4c416c20a1c (angular/angular)

Patch available: angular/angular v20.3.28 (contains commit e4c416c20a1c)

https://github.com/angular/angular/commit/e4c416c20a1cb222ce73d29c035452b257380c56
github_commit Patch Available

commit caf616670fd2 (angular/angular)

Patch available: angular/angular v21.2.20 (contains commit caf616670fd2)

https://github.com/angular/angular/commit/caf616670fd20d528aa69e0131cc17d60f0cc27d
github_commit

commit c45028e44f5f (angular/angular)

Fix landed in angular/angular commit c45028e44f5f — awaiting tagged release

https://github.com/angular/angular/commit/c45028e44f5f3c1e0006eaccf86642deca51b2af

Vendor Advisories for CVE-2026-88059(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)
PackageVulnerable rangeFixed inDependents
@angular/common22.1.1

Weakness Classification(2)

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

Data Freshness Timeline

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

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 13:48 UTCEG score recompute
  3. 2026-09-17 19:32 UTCEPSS rescore
  4. 2026-09-16 15:05 UTCEG score recompute
  5. 2026-09-16 14:09 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 15:47 UTCEG score recompute
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-13 17:11 UTCEG score recompute
  10. 2026-09-13 16:48 UTCEPSS rescore
  11. 2026-09-12 17:53 UTCEG score recompute
  12. 2026-09-12 15:02 UTCEPSS rescore
  13. 2026-09-11 18:35 UTCEG score recompute
  14. 2026-09-11 17:54 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-10 19:18 UTCEG score recompute
  18. 2026-09-10 19:10 UTCEG score recompute
  19. 2026-09-10 19:09 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-88059?
CVE-2026-88059 is a medium vulnerability published on September 10, 2026. Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.28, 21.2.20, and 22.1.1, Angular's @angular/common HttpTransferCache can cache an authenticated response when Server-Side Rendering (SSR) and hydration…
When was CVE-2026-88059 disclosed?
CVE-2026-88059 was first published in the National Vulnerability Database on September 10, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-88059 actively exploited?
CVE-2026-88059 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.5% of all scored CVEs.
What is the CVSS score of CVE-2026-88059?
CVE-2026-88059 has a CVSS v3 base score of 4.0 (NVD).
How do I remediate CVE-2026-88059?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-88059, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-88059?

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