CVE-2026-88056

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.5% (45th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-75675 (ENISA EUVD) · GHSA-f6mr-pjwc-34m4 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.1Exploit: No code on recordExposed 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.30, 21.2.22, and 22.1.4, Angular Server-Side Rendering in @angular/platform-server processes user-controlled resource or request URLs through HttpClient after application code validates them with WHATWG URL parsing. The resolveUrl and parseUrl utilities called String.prototype.trim(), which removed leading Unicode whitespace such as U+00A0 or U+FEFF after the input passed a same-origin check, converting a relative path into a protocol-relative attacker-controlled URL. In affected applications that attach sensitive server-side credentials such as Authorization headers to approved requests, relativeUrlsTransformerInterceptorFn then dispatched the request to the attacker-controlled origin, causing SSRF and credential disclosure. This issue is fixed in versions 20.3.30, 21.2.22, and 22.1.4.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
45th
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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 low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 (7)

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

22.1.4

Patch available: angular/angular v22.1.4

https://github.com/angular/angular/releases/tag/v22.1.4
GitHub release Patch Available

21.2.22

Patch available: angular/angular v21.2.22

https://github.com/angular/angular/releases/tag/v21.2.22
GitHub release Patch Available

20.3.30

Patch available: angular/angular v20.3.30

https://github.com/angular/angular/releases/tag/v20.3.30
GitHub commit Patch Available

commit 71e52d1396b9 (angular/angular)

Patch available: angular/angular v22.1.4 (contains commit 71e52d1396b9)

https://github.com/angular/angular/commit/71e52d1396b9cef98652929b73e08c4cde645970
GitHub commit Patch Available

commit 5aa6d97deb9e (angular/angular)

Patch available: angular/angular v21.2.22 (contains commit 5aa6d97deb9e)

https://github.com/angular/angular/commit/5aa6d97deb9ef1de14e23748b7fa74f97d183132
GitHub commit Patch Available

commit 3e924cc8dbbb (angular/angular)

Patch available: angular/angular v22.2.0-next.4 (contains commit 3e924cc8dbbb)

https://github.com/angular/angular/commit/3e924cc8dbbb57f23b262cb8f0d7e2bd0673034c
GitHub advisoryMentions a patch (unverified)

SSRF and Cross-Origin Credential Disclosure via URL Resolution Discrepancy in SSR · Advisory · angular/angular · GitHub

https://github.com/angular/angular/security/advisories/GHSA-f6mr-pjwc-34m4

Vendor Advisories for CVE-2026-88056(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/platform-server @ 22.1.4 (fixes >= 22.0.0, < 22.1.4)—ghsa
npm@angular/platform-server @ 21.2.22 (fixes >= 21.0.0, < 21.2.22)—ghsa
npm@angular/platform-server @ 20.3.30 (fixes >= 20.0.0, < 20.3.30)—ghsa
npm@angular/platform-server—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/platform-server—
  • 22.0.0 up to 22.1.4: fixed in 22.1.4
  • 21.0.0 up to 21.2.22: fixed in 21.2.22
  • 20.0.0 up to 20.3.30: fixed in 20.3.30
  • every version through 19.2.25: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 111 refreshes on record for this CVE.

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. None are among the latest 100 rows. The 11 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 19:22 UTCEG score recompute
  2. 2026-11-01 19:22 UTCGHSA enrichmentGHSA-f6mr-pjwc-34m4 · GitHub severity HIGH
  3. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  4. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-f6mr-pjwc-34m4 · GitHub severity HIGH
  5. 2026-10-31 17:15 UTCEG score recompute
  6. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  7. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  8. 2026-10-30 15:08 UTCEG score recompute
  9. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  10. 2026-10-29 13:02 UTCEG score recompute
  11. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  12. 2026-10-28 10:55 UTCEG score recompute
  13. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  14. 2026-10-27 07:52 UTCEG score recompute
  15. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  16. 2026-10-26 03:10 UTCEG score recompute
  17. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  18. 2026-10-25 13:53 UTCEG score recompute
  19. 2026-10-25 01:04 UTCEG score recompute
  20. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-10-23 22:55 UTCEG score recompute
  22. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-10-22 20:48 UTCEG score recompute
  24. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  25. 2026-10-21 18:39 UTCEG score recompute
Show 75 more
  1. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-10-20 16:33 UTCEG score recompute
  4. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-10-19 14:18 UTCEG score recompute
  6. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-10-18 03:03 UTCEG score recompute
  8. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-10-17 10:03 UTCEG score recompute
  10. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-16 07:56 UTCEG score recompute
  12. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  13. 2026-10-15 05:49 UTCEG score recompute
  14. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  15. 2026-10-14 01:26 UTCEG score recompute
  16. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-12 21:37 UTCEG score recompute
  18. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-10-12 14:49 UTCEG score recompute
  20. 2026-10-11 19:15 UTCEG score recompute
  21. 2026-10-11 16:32 UTCEG score recompute
  22. 2026-10-11 16:09 UTCEG score recompute
  23. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-11 13:49 UTCEG score recompute
  25. 2026-10-11 11:45 UTCEG score recompute
  26. 2026-10-10 23:16 UTCEG score recompute
  27. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  28. 2026-10-10 00:13 UTCEG score recompute
  29. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  30. 2026-10-08 23:45 UTCEG score recompute
  31. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  32. 2026-10-08 00:18 UTCEG score recompute
  33. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  34. 2026-10-06 15:48 UTCEG score recompute
  35. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  36. 2026-10-05 20:49 UTCEG score recompute
  37. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  38. 2026-10-05 03:14 UTCEG score recompute
  39. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  40. 2026-10-03 14:49 UTCEG score recompute
  41. 2026-10-02 19:04 UTCEG score recompute
  42. 2026-10-02 00:22 UTCEG score recompute
  43. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  44. 2026-09-30 15:07 UTCEG score recompute
  45. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  46. 2026-09-29 19:13 UTCEG score recompute▲ 0.50
  47. 2026-09-29 19:06 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  48. 2026-09-28 21:42 UTCEG score recompute
  49. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  50. 2026-09-27 23:05 UTCEG score recompute
  51. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  52. 2026-09-27 00:21 UTCEG score recompute
  53. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  54. 2026-09-26 01:26 UTCEG score recompute
  55. 2026-09-24 15:13 UTCEG score recompute
  56. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  57. 2026-09-24 03:53 UTCEG score recompute
  58. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  59. 2026-09-22 17:44 UTCEG score recompute
  60. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  61. 2026-09-22 06:08 UTCEG score recompute
  62. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  63. 2026-09-21 07:30 UTCEG score recompute
  64. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  65. 2026-09-19 21:33 UTCEG score recompute
  66. 2026-09-18 22:55 UTCEG score recompute
  67. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  68. 2026-09-18 00:18 UTCEG score recompute
  69. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  70. 2026-09-16 14:11 UTCEG score recompute
  71. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  72. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  73. 2026-09-15 15:33 UTCEG score recompute
  74. 2026-09-15 15:03 UTCEG score recompute
  75. 2026-09-15 13:07 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-88056?
CVE-2026-88056 is a critical-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.30, 21.2.22, and 22.1.4, Angular Server-Side Rendering in @angular/platform-server processes user-controlled resource or request URLs through HttpClient…
When was the CVE record for CVE-2026-88056 published?
The CVE record for CVE-2026-88056 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-88056 actively exploited?
CVE-2026-88056 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-88056?
CVE-2026-88056 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-88056?
A fix for CVE-2026-88056 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-88056 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-88056

Explore →

Is Your Infrastructure Affected by CVE-2026-88056?

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