CVE-2026-41423: Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server

Published May 8, 2026
·
Updated

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.21, 20.3.19, 21.2.9, and 22.0.0-next.8, 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. This issue has been patched in versions 19.2.21, 20.3.19, 21.2.9, and 22.0.0-next.8.

Affected Software

13 affected components
npm/@angular/platform-server<19.2.21, <20.3.19, <21.2.9, <22.0.0-next.8
angular Angular Node.js<19.2.21
angular Angular Node.js>=20.0.0<20.3.19
angular Angular Node.js>=21.0.0<21.2.9
angular Angular Node.js=22.0.0-next0
angular Angular Node.js=22.0.0-next1
angular Angular Node.js=22.0.0-next2
angular Angular Node.js=22.0.0-next3
angular Angular Node.js=22.0.0-next4
angular Angular Node.js=22.0.0-next5
angular Angular Node.js=22.0.0-next6
angular Angular Node.js=22.0.0-next7
angular Angular Node.js=22.0.0-next8

Event History

May 8, 2026
CVE Published
via MITRE·01:06 PM
Data Sourced
via MITRE·01:06 PM
DescriptionWeakness
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-41423?

CVE-2026-41423 has been rated as a critical vulnerability due to its potential for Server-Side Request Forgery (SSRF) exploitation.

2

How do I fix CVE-2026-41423?

To fix CVE-2026-41423, upgrade to Angular Platform-Server versions 19.2.21, 20.3.19, 21.2.9, or 22.0.0-next.8 or later.

3

What versions of Angular Platform-Server are affected by CVE-2026-41423?

Angular Platform-Server versions prior to 19.2.21, 20.3.19, 21.2.9, and 22.0.0-next.8 are affected by CVE-2026-41423.

4

What types of applications are impacted by CVE-2026-41423?

CVE-2026-41423 impacts web applications built using Angular Platform-Server that may be vulnerable to SSRF via certain URL formats.

5

What specific vulnerabilities are associated with CVE-2026-41423?

CVE-2026-41423 allows SSRF through the use of protocol-relative and backslash URLs in Angular Platform-Server.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203