← Back
CVE-2026-41423
medium
CVSS 5.3
SSRF (Server-Side Request Forgery) in @angular/platform-server (CVE-2026-41423)
Summary
SSRF in @angular/platform-server (CVE-2026-41423). Risk of unauthorized operations or information disclosure. Exploitable via ``evil.com``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41423** has been found in @angular/platform-server.
Attackers can target a specific entry point like ``evil.com`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "@angular/platform-server CVE-2026-41423" on the vendor's site.
CVE-2026-41423 (@angular/platform-server) — CWE-918 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `evil.com` / `HttpClient` / `PlatformLocation.hostname` / `renderModule`
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 ``evil.com`` without authentication.
📍 Affected scope
@angular/platform-server — . Attack surface: `evil.com` / `HttpClient` / `PlatformLocation.hostname` / `renderModule`.
🔥 Severity
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure
🔧 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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@angular/platform-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@angular/platform-server` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@angular/platform-server
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"18.2.14"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-41423
- package https://github.com/angular/angular
- web https://github.com/angular/angular/commit/ede7c58a2aa13fdccc8f0b67ce93ba1c11749412
- web https://github.com/angular/angular/pull/68194
- web https://github.com/angular/angular/security/advisories/GHSA-45q2-gjvg-7973
- web https://github.com/advisories/GHSA-45q2-gjvg-7973