@angular/platform-server
Affected
- introduced
22.0.0-next.0, fixed22.0.0-next.8(semver)
Fixed versions
22.0.0-next.8
Fix
- Fixed version
22.0.0-next.8npm install @angular/[email protected]
Advisory
Also known as: CVE-2026-41423
Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server
Impact
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.
Affected APIs:
renderModulerenderApplicationCommonEngine (from @angular/ssr)Non-Affected APIs:
AngularAppEngine (from @angular/ssr)AngularNodeAppEngine (from @angular/ssr)Attack Preconditions
req.url).HttpClient with relative URLs or uses PlatformLocation.hostname to build URLs. Patches
Workarounds
Developers should implement a middleware to sanitize the request URL before it reaches Angular. This involves stripping or normalizing leading slashes:
app.use((req, res, next) => {
// Sanitize the URL to ensure it starts with a single forward slash
if (req.url.startsWith('//') || req.url.startsWith('/\\') || req.url.startsWith('\\')) {
req.url = '/' + req.url.replace(/^[/\\]+/, '');
}
next();
});
References
High Basis: The source's own band: HIGH
22.0.0-next.0, fixed 22.0.0-next.8 (semver)22.0.0-next.8
22.0.0-next.8npm install @angular/[email protected]21.0.0-next.0, fixed 21.2.9 (semver)21.2.9
21.2.9npm install @angular/[email protected]20.0.0-next.0, fixed 20.3.19 (semver)20.3.19
20.3.19npm install @angular/[email protected]19.0.0-next.0, fixed 19.2.21 (semver)19.2.21
19.2.21npm install @angular/[email protected]0, last affected 18.2.14 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0