Advisory

GHSA-xh43-g2fq-wjrj

Also known as: CVE-2026-27738

Summary

Angular SSR has an Open Redirect via X-Forwarded-Prefix

Details

An Open Redirect vulnerability exists in the internal URL processing logic in Angular SSR. The logic normalizes URL segments by stripping leading slashes; however, it only removes a single leading slash.

When an Angular SSR application is deployed behind a proxy that passes the X-Forwarded-Prefix header, an attacker can provide a value starting with three slashes (e.g., ///evil.com).

  1. The application processes a redirect (e.g., from a router redirectTo or i18n locale switch).
  2. Angular receives ///evil.com as the prefix.
  3. It strips one slash, leaving //evil.com.
  4. The resulting string is used in the Location header.
  5. Modern browsers interpret // as a protocol-relative URL, redirecting the user from https://your-app.com to https://evil.com.

Impact
This vulnerability allows attackers to conduct large-scale phishing and SEO hijacking:

  • Scale: A single request can poison a high-traffic route, impacting all users until the cache expires.
  • SEO Poisoning: Search engine crawlers may follow and index these malicious redirects, causing the legitimate site to be delisted or associated with malicious domains.
  • Trust: Because the initial URL belongs to the trusted domain, users and security tools are less likely to flag the redirect as malicious.

Attack Preconditions

  • The application must use Angular SSR.
  • The application must have routes that perform internal redirects.
  • The infrastructure (Reverse Proxy/CDN) must pass the X-Forwarded-Prefix header to the SSR process without sanitization.
  • The cache must not vary on the X-Forwarded-Prefix header.

Patches

  • 21.2.0-rc.1
  • 21.1.5
  • 20.3.17
  • 19.2.21

Workarounds
Until the patch is applied, developers should sanitize the X-Forwarded-Prefix header in theirserver.ts before the Angular engine processes the request:

app.use((req, res, next) => {
  const prefix = req.headers['x-forwarded-prefix']?.trim();
  if (prefix) {
    // Sanitize by removing all leading slashes
    req.headers['x-forwarded-prefix'] = prefix.replace(/^[/\\]+/, '/');
  }
  next();
});

Resources

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-02-25 22:41 UTC
Modified
2026-04-02 13:44 UTC

Affected packages and fixes

@angular/ssr

npm · All systems

Affected

  • introduced 21.2.0-next.0, fixed 21.2.0-rc.1 (semver)

Fixed versions

21.2.0-rc.1

Fix

@angular/ssr

npm · All systems

Affected

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

Fixed versions

21.1.5

Fix

@angular/ssr

npm · All systems

Affected

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

Fixed versions

20.3.17

Fix

@angular/ssr

npm · All systems

Affected

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

Fixed versions

19.2.21

Fix

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