CVE-2026-88059

MEDIUMNVD 5.85.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 5.8 under NVD CVSS v3. EPSS exploit probability: 0.3% (27th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.0 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-09-10) is not newer than that change (2026-09-29), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-75702 (ENISA EUVD) · GHSA-p297-fm68-3q8c (GitHub Security Advisories)Source: ENISA EUVD

5.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.8Exploit: 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 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
5.8
EG Score
5.8MEDIUMmedium confidence
EG Risk
26
EG Risk 26/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity58% × 45%
Impact severity (EG Severity): CVSS 5.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
27th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.8): severity, escalated by confirmed exploitation. This CVE's 5.8 is its impact severity (EG Severity), not escalated.

EG Severity
5.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 10, 2026

Last Modified

September 29, 2026

Advisory Details (9)

Auto-updated Sep 10, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)

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 pull request 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
Web page

`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.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@angular/common @ 22.1.1 (fixes >= 22.0.0, < 22.1.1)—ghsa
npm@angular/common @ 21.2.20 (fixes >= 21.0.0, < 21.2.20)—ghsa
npm@angular/common @ 20.3.28 (fixes >= 20.0.0, < 20.3.28)—ghsa
npm@angular/common—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
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
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@angular/common—
  • 22.0.0 up to 22.1.1: fixed in 22.1.1
  • 21.0.0 up to 21.2.20: fixed in 21.2.20
  • 20.0.0 up to 20.3.28: fixed in 20.3.28
  • every version through 19.2.25: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 91 is merged into the row it repeats.

  1. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  3. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-p297-fm68-3q8c · GitHub severity MODERATE · GitHub CVSS 4.0
  4. 2026-11-01 07:37 UTCEG score recompute
  5. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  6. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  7. 2026-10-29 22:55 UTCOSV refresh
  8. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  9. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  11. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  12. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  13. 2026-10-25 13:53 UTCEG score recompute
  14. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  17. 2026-10-22 12:34 UTCEG score recompute
  18. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  19. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-10-18 03:03 UTCEG score recompute
  23. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  25. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
Show 65 more
  1. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  2. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  3. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  4. 2026-10-12 14:49 UTCEG score recompute
  5. 2026-10-11 19:15 UTCEG score recompute
  6. 2026-10-11 16:32 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-10-11 13:49 UTCEG score recompute
  9. 2026-10-10 23:16 UTCEG score recompute
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  11. 2026-10-09 23:02 UTCEG score recompute
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-10-08 23:44 UTCEG score recompute
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-10-06 16:51 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  18. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-10-05 17:34 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-10-03 18:58 UTCEG score recompute
  22. 2026-10-02 19:16 UTCEG score recompute
  23. 2026-10-01 19:57 UTCEG score recompute
  24. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  25. 2026-09-30 20:40 UTCEG score recompute
  26. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  27. 2026-09-29 21:21 UTCEG score recompute▲ 1.80
  28. 2026-09-29 21:18 UTCNVD updateCVSS v3 → 5.8
  29. 2026-09-29 06:29 UTCEG score recompute
  30. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  31. 2026-09-28 07:11 UTCEG score recompute
  32. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  33. 2026-09-27 07:54 UTCEG score recompute
  34. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  35. 2026-09-26 08:36 UTCEG score recompute
  36. 2026-09-25 08:59 UTCEG score recompute
  37. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  38. 2026-09-24 09:41 UTCEG score recompute
  39. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  40. 2026-09-23 10:23 UTCEG score recompute
  41. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  42. 2026-09-22 11:05 UTCEG score recompute
  43. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  44. 2026-09-21 11:47 UTCEG score recompute
  45. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  46. 2026-09-20 12:29 UTCEG score recompute
  47. 2026-09-19 13:06 UTCEG score recompute
  48. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  49. 2026-09-18 13:48 UTCEG score recompute
  50. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  51. 2026-09-16 15:05 UTCEG score recompute
  52. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  53. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  54. 2026-09-15 15:47 UTCEG score recompute
  55. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  56. 2026-09-13 17:11 UTCEG score recompute
  57. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  58. 2026-09-12 17:53 UTCEG score recompute
  59. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  60. 2026-09-11 18:35 UTCEG score recompute
  61. 2026-09-11 17:54 UTCEG score recompute
  62. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  63. 2026-09-10 19:18 UTCEG score recompute
  64. 2026-09-10 19:10 UTCEG score recomputeFirst assessed: 4.0 MEDIUM
  65. 2026-09-10 19:09 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-88059?
CVE-2026-88059 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-88059 published?
The CVE record for CVE-2026-88059 was published on September 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 29, 2026; the record at its source may have been updated since.
Is CVE-2026-88059 actively exploited?
CVE-2026-88059 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-88059?
CVE-2026-88059 has a CVSS v3 base score of 5.8 (NVD).
How do I remediate CVE-2026-88059?
A fix for CVE-2026-88059 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-88059 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-88059

Explore →

Is Your Infrastructure Affected by CVE-2026-88059?

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

Book a Demo →Browse All CVEs