Platform server: Angular: SSRF and Cross-Origin Credential Disclosure via URL Resolution Discrepancy in SSR (CVE-2026-88056)
A vulnerability in @angular/platform-server's Server-Side Rendering (SSR) URL resolution allows attackers to bypass same-origin checks due to a discrepancy in Unicode whitespace handling between WHATWG URL parsing and Angular's URL utilities. This can lead to Server-Side Request Forgery (SSRF) and leakage of sensitive server-side credentials such as Authorization headers. The issue arises because Angular's URL resolution trims Unicode whitespace characters that WHATWG URL parsing does not, causing URLs with leading non-breaking spaces to be misinterpreted and routed to attacker-controlled domains. This affects Angular SSR applications that attach sensitive credentials to requests after performing same-origin validation using WHATWG URL parsing. Workarounds include sanitizing input URLs to remove leading Unicode whitespace before validation and not relying solely on WHATWG URL origin checks when input may be trimmed differently.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-88056) in @angular/platform-server involves a mismatch in URL parsing behavior between the WHATWG URL standard and Angular SSR's URL resolution utilities. Specifically, URLs containing leading Unicode whitespace characters such as NO-BREAK SPACE (U+00A0) pass same-origin checks when validated with WHATWG URL parsing because these characters are not stripped. However, Angular's URL resolution functions trim these characters using JavaScript's String.prototype.trim(), which removes all Unicode whitespace, converting the URL into a cross-origin protocol-relative URL. This causes server-side HTTP requests to be sent to attacker-controlled origins, leaking sensitive credentials attached to the request. The vulnerability affects Angular SSR applications that use HttpClient with user-controlled URLs and attach sensitive headers after same-origin validation. The affected versions are Angular platform-server versions >=20.0.0 <20.3.30, >=21.0.0 <21.2.22, >=22.0.0 <22.1.4, and <=19.2.25. A patch is available.
Potential Impact
Exploitation allows attackers to bypass same-origin validation in Angular SSR applications, triggering Server-Side Request Forgery (SSRF) and leaking sensitive server-side credentials such as Authorization headers or API keys. This can lead to unauthorized access or data exfiltration from the server environment. The vulnerability is reachable when user input influences URLs processed by Angular's HttpClient and sensitive credentials are attached to requests after origin checks.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade to fixed versions of @angular/platform-server as indicated by the vendor. Until patched, applications should sanitize input URLs to disallow leading Unicode whitespace characters (e.g., U+00A0) before performing origin checks or passing them to HttpClient. Additionally, do not rely solely on WHATWG URL origin validation if the input may be trimmed or normalized differently by other utilities. Follow vendor advisories for official remediation guidance.
Platform server: Angular: SSRF and Cross-Origin Credential Disclosure via URL Resolution Discrepancy in SSR (CVE-2026-88056)
Description
A vulnerability in @angular/platform-server's Server-Side Rendering (SSR) URL resolution allows attackers to bypass same-origin checks due to a discrepancy in Unicode whitespace handling between WHATWG URL parsing and Angular's URL utilities. This can lead to Server-Side Request Forgery (SSRF) and leakage of sensitive server-side credentials such as Authorization headers. The issue arises because Angular's URL resolution trims Unicode whitespace characters that WHATWG URL parsing does not, causing URLs with leading non-breaking spaces to be misinterpreted and routed to attacker-controlled domains. This affects Angular SSR applications that attach sensitive credentials to requests after performing same-origin validation using WHATWG URL parsing. Workarounds include sanitizing input URLs to remove leading Unicode whitespace before validation and not relying solely on WHATWG URL origin checks when input may be trimmed differently.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-88056) in @angular/platform-server involves a mismatch in URL parsing behavior between the WHATWG URL standard and Angular SSR's URL resolution utilities. Specifically, URLs containing leading Unicode whitespace characters such as NO-BREAK SPACE (U+00A0) pass same-origin checks when validated with WHATWG URL parsing because these characters are not stripped. However, Angular's URL resolution functions trim these characters using JavaScript's String.prototype.trim(), which removes all Unicode whitespace, converting the URL into a cross-origin protocol-relative URL. This causes server-side HTTP requests to be sent to attacker-controlled origins, leaking sensitive credentials attached to the request. The vulnerability affects Angular SSR applications that use HttpClient with user-controlled URLs and attach sensitive headers after same-origin validation. The affected versions are Angular platform-server versions >=20.0.0 <20.3.30, >=21.0.0 <21.2.22, >=22.0.0 <22.1.4, and <=19.2.25. A patch is available.
Potential Impact
Exploitation allows attackers to bypass same-origin validation in Angular SSR applications, triggering Server-Side Request Forgery (SSRF) and leaking sensitive server-side credentials such as Authorization headers or API keys. This can lead to unauthorized access or data exfiltration from the server environment. The vulnerability is reachable when user input influences URLs processed by Angular's HttpClient and sensitive credentials are attached to requests after origin checks.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade to fixed versions of @angular/platform-server as indicated by the vendor. Until patched, applications should sanitize input URLs to disallow leading Unicode whitespace characters (e.g., U+00A0) before performing origin checks or passing them to HttpClient. Additionally, do not rely solely on WHATWG URL origin validation if the input may be trimmed or normalized differently by other utilities. Follow vendor advisories for official remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-f6mr-pjwc-34m4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-88056"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6aa3295e91cc7f3848d18df4
Added to database: 09/10/2026, 22:04:14 UTC
Last enriched: 09/10/2026, 22:06:16 UTC
Last updated: 09/10/2026, 22:13:56 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.