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.
CVE-2026-88056
This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). 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).
- 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
- 8.6
- EG Score
- 8.6(medium)
- EG Risk
- 70(Attend)EG Risk 70/100SSVC: Attend
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 computedSeverity86% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 36%
- KEV
- Not listed
Published
September 10, 2026
Last Modified
September 15, 2026
Advisory Details (7)
Auto-updated Sep 10, 202622.1.4
Patch available: angular/angular v22.1.4
https://github.com/angular/angular/releases/tag/v22.1.421.2.22
Patch available: angular/angular v21.2.22
https://github.com/angular/angular/releases/tag/v21.2.2220.3.30
Patch available: angular/angular v20.3.30
https://github.com/angular/angular/releases/tag/v20.3.30commit 71e52d1396b9 (angular/angular)
Patch available: angular/angular v22.1.4 (contains commit 71e52d1396b9)
https://github.com/angular/angular/commit/71e52d1396b9cef98652929b73e08c4cde645970commit 5aa6d97deb9e (angular/angular)
Patch available: angular/angular v21.2.22 (contains commit 5aa6d97deb9e)
https://github.com/angular/angular/commit/5aa6d97deb9ef1de14e23748b7fa74f97d183132commit 3e924cc8dbbb (angular/angular)
Patch available: angular/angular v22.2.0-next.4 (contains commit 3e924cc8dbbb)
https://github.com/angular/angular/commit/3e924cc8dbbb57f23b262cb8f0d7e2bd0673034cSSRF 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-34m4Vendor 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.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @angular/platform-server | — | 22.1.4 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 22× 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-09-19 21:33 UTCEG score recompute
- 2026-09-18 22:55 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 00:18 UTCEG score recompute
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 14:11 UTCEG score recompute
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 15:33 UTCEG score recompute
- 2026-09-15 15:03 UTCEG score recompute
- 2026-09-15 13:07 UTCEG score recompute
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 03:10 UTCEG score recompute
- 2026-09-13 16:48 UTCEPSS rescore
- 2026-09-12 17:14 UTCEG score recompute
- 2026-09-12 15:02 UTCEPSS rescore
- 2026-09-11 18:36 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 19:18 UTCEG score recompute
- 2026-09-10 18:50 UTCEG score recompute
- 2026-09-10 18:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-88056?
When was CVE-2026-88056 disclosed?
Is CVE-2026-88056 actively exploited?
What is the CVSS score of CVE-2026-88056?
How do I remediate CVE-2026-88056?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-88056
Is Your Infrastructure Affected by CVE-2026-88056?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.