ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-88056

SSRF and Cross-Origin Credential Disclosure via URL Resolution Discrepancy in SSR

Published Aug 27, 2026 · catalog updated Sep 10, 2026 · SSRF and Cross-Origin Credential

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-88056. EPSS is 0.54%. Act only if a listed version of SSRF and Cross-Origin Credential is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (SSRF and Cross-Origin Credential).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.54%
Remediation
Version ranges on file
Affected products
npm @angular/platform-server

### Summary A discrepancy between WHATWG URL parsing and Angular SSR's URL resolution allows attackers to bypass same-origin checks and cause Server-Side Request Forgery (SSRF), potentially leaking sensitive server-side credentials. ### Technical Description When applications validate incoming URLs using the WHATWG URL standard ( ), Unicode whitespace characters (such as NO-BREAK SPACE or ZERO WIDTH NO-BREAK SPACE ) are not stripped and are evaluated as part of a same-origin relative path (e.g. ). Consequently, these URLs successfully pass application-level same-origin checks. However, 's URL resolution utility ( / ) previously executed . Because JavaScript's strips all Unicode whitespace (including ), the leading non-breaking space was removed, converting the string into a cross-origin protocol-relative URL ( ). When resolved during server-side rendering (such as in ), this caused the HTTP request to be dispatched to the attacker-controlled origin ( ), leaking any credentials (such as headers) attached by the application for the intended same-origin request. ### Impact & Reachability * **Reachability**: The vulnerability affects Angular Server-Side Rendering (SSR) applications where user-controlled input influences resource or request URLs processed by Angular's , an application-level same-origin check is performed before dispatching, and sensitive server-side credentials (such as API keys or Bearer tokens) are attached to approved requests. * **Impact**: Successful exploitation allows attackers to bypass same-origin validation, triggering Server-Side Request Forgery (SSRF) and leaking sensitive server-side credentials attached to the request. **Proof of Concept:** ### Workarounds * Validate and sanitize input URLs to disallow leading Unicode whitespace characters (such as ) before performing origin checks or passing them to . * Avoid relying solely on for authorization if the input string may be trimmed or processed by utilities that normalize whitespace different

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm @angular/platform-server<= 19.2.25
  • npm @angular/platform-server>= 20.0.0, < 20.3.30
  • npm @angular/platform-server>= 21.0.0, < 21.2.22
  • npm @angular/platform-server>= 22.0.0, < 22.1.4

How to fix CVE-2026-88056

  • Upgrade

    CVE-2026-88056 lists a fix boundary at 19.2.25. Compare the installed build with that boundary before you change production.

  • Version check

    Affected <= 19.2.25

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-88056. EPSS is 0.54%. Act only if a listed version of SSRF and Cross-Origin Credential is installed.

Which versions are affected?

Compare what you have installed with <= 19.2.25, >= 20.0.0, < 20.3.30, >= 21.0.0, < 21.2.22, >= 22.0.0, < 22.1.4. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-918: Server-Side Request Forgery (SSRF). EPSS 0.54%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Angular security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 27, 2026 · Maintainer security tabs

    Detected

    ### Summary A discrepancy between WHATWG URL parsing and Angular SSR's URL resolution allows attackers to bypass same-origin checks and cause Server-Side Request Forgery (SSRF), potentially leaking sensitive server-side credentials. ### Technical Description When applications validate incoming URLs using the WHATWG URL standard ( ), Unicode whitespace characters (such as NO-BREAK SPACE or ZERO WID

  2. Sep 10, 2026 · Maintainer security tabs

    Updated

    ### Summary A discrepancy between WHATWG URL parsing and Angular SSR's URL resolution allows attackers to bypass same-origin checks and cause Server-Side Request Forgery (SSRF), potentially leaking sensitive server-side credentials. ### Technical Description When applications validate incoming URLs using the WHATWG URL standard ( ), Unicode whitespace characters (such as NO-BREAK SPACE or ZERO WID

Sources

  • Maintainer security tabsVendor advisoryGHSA-f6mr-pjwc-34m4

    ### Summary A discrepancy between WHATWG URL parsing and Angular SSR's URL resolution allows attackers to bypass same-origin checks and cause Server-Side Request Forgery (SSRF), potentially leaking sensitive server-side credentials. ### Technical Description When applications validate incoming URLs using the WHATWG URL standard ( ), Unicode whitespace characters (such as NO-BREAK SPACE or ZERO WID

    github.com

Freshness

Last verified in this catalog Nov 2, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 2, 2026