Servers and applications
CVE-2026-41423
SSRF via protocol-relative and backslash URLs in Angular Platform-Server
- Severity
- High 8.7
- Published
- 16 Apr 2026
- Last changed
- 20 Apr 2026
- Added to UpHeron
- 3 Nov 2026
- Exploit chance
- 0.3% in the next 30 daysHigher than 23% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:N- Also known as
- GHSA-45q2-gjvg-7973
- Sources
- Project advisories (GitHub)
Description
A Server-Side Request Forgery (SSRF) vulnerability exists in @angular/platform-server due to improper handling of URLs during Server-Side Rendering (SSR).
When an attacker sends a request such as GET /\evil.com/ HTTP/1.1 the server engine (Express, etc.) passes the URL string to Angular’s rendering functions.
Because the URL parser normalizes the backslash to a forward slash for HTTP/HTTPS schemes, the internal state of the application is hijacked to believe the current origin is evil.com. This misinterpretation tricks the application into treating the attacker’s domain as the local origin. Consequently, any relative HttpClient requests or PlatformLocation.hostname references are redirected to the attacker controlled server, potentially exposing internal APIs or metadata services.
- The server has outbound network access.
- The application uses Angular SSR via the affected APIs.
- A pathname is passed as URL to the rendering method (e.g. using req.url).
Workarounds
Developers should implement a middleware to sanitize the request URL before it reaches Angular. This involves stripping or normalizing leading slashes:
Affected software
| Software | Affected versions |
|---|---|
AngularServers and applications · github:angular/angular |
|
About Angular
web application framework
- Developers who used it in the past year
- 18.2%Stack Overflow Developer Survey 2025, 2025
- Weekly downloads (npm)
- 8,195,583npm, 15 Nov 2026
- GitHub stars
- 101,504GitHub, 15 Nov 2026
- Forks
- 28,216GitHub, 15 Nov 2026
- Latest release
- v22.2.6GitHub, 15 Nov 2026
- Released
- 12 Nov 2026GitHub
- Developer
- GoogleWikidata
- License
- MIT LicenseWikidata
- Written in
- TypeScriptWikidata
- First released
- 15 Sept 2016Wikidata
- First published on GitHub
- 18 Sept 2014GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 22 | 22.2.6 | Until 30 Jun 2028 |
| 21 | 21.2.26 | Until 30 Jun 2027 |
| 20 | 20.3.35 | Until 28 Nov 2026 |
| 19 | 19.2.25 | Ended 19 May 2026 |
| 18 | 18.2.14 | Ended 21 Nov 2025 |
| 17 | 17.3.12 | Ended 15 May 2025 |
From endoflife.date.
Vulnerabilities in Angular
- In our list
- 39
- Published in the last 12 months
- 38
- Critical, last 12 months
- 1
- High, last 12 months
- 26
- Known exploited
- 0
- GHSA-ffj9-42qx-f38hCross-Site Scripting (XSS) via AngularJS Double Compilation in @angular/upgrade's downgradeComponent()Medium 6.3 9 Nov 2026
- CVE-2026-111753XSRF Token Leakage via URL Parsing Discrepancy in Angular HTTP Client (Incomplete fix for CVE-2025-66035)Medium 5.9 16 Oct 2026
- CVE-2026-111751Denial of Service via RouterLink Query Parameter Retention in Server-Side Rendering (SSR)High 8.2 1 Oct 2026
- CVE-2026-111752Denial of Service via Unmatched Empty-Path Outlet Route Matching in Server-Side Rendering (SSR)High 8.2 30 Sept 2026
- CVE-2026-111754Open Redirect via Protocol-Relative URLs in Server-Side Rendering (SSR)Medium 5.1 30 Sept 2026
- CVE-2026-101896Denial of Service via Numeric URL Matrix Parameters in Server-Side Rendering (SSR)High 8.2 23 Sept 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-41423
- GitHub Advisory Database https://github.com/advisories/GHSA-45q2-gjvg-7973
- github.com https://github.com/angular/angular/security/advisories/GHSA-45q2-gjvg-7973