Advisory

GHSA-45q2-gjvg-7973

Also known as: CVE-2026-41423

Summary

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

Details

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:

  • renderModule
  • renderApplication
  • CommonEngine (from @angular/ssr)

Non-Affected APIs:

  • AngularAppEngine (from @angular/ssr)
  • AngularNodeAppEngine (from @angular/ssr)

Attack Preconditions

  • 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).
  • The server-side code performs HTTP requests using HttpClient with relative URLs or uses PlatformLocation.hostname to build URLs.

Patches

  • 22.0.0-next.8
  • 21.2.9
  • 20.3.19
  • 19.2.21

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

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-04-16 22:36 UTC
Modified
2026-05-12 17:16 UTC

Affected packages and fixes

@angular/platform-server

npm · All systems

Affected

  • introduced 22.0.0-next.0, fixed 22.0.0-next.8 (semver)

Fixed versions

22.0.0-next.8

Fix

@angular/platform-server

npm · All systems

Affected

  • introduced 21.0.0-next.0, fixed 21.2.9 (semver)

Fixed versions

21.2.9

Fix

@angular/platform-server

npm · All systems

Affected

  • introduced 20.0.0-next.0, fixed 20.3.19 (semver)

Fixed versions

20.3.19

Fix

@angular/platform-server

npm · All systems

Affected

  • introduced 19.0.0-next.0, fixed 19.2.21 (semver)

Fixed versions

19.2.21

Fix

@angular/platform-server

npm · All systems

Affected

  • introduced 0, last affected 18.2.14 (semver)

Fixed versions

None listed

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences