CVE-2026-27738: @angular/ssr Angular SSR Has An Open Vulnerability

MODERATE
Advisory Identifier: GHSA-xh43-g2fq-wjrj
CWE-601
Published
Advisory Summary

CVE-2026-27738 is a MODERATE angular ssr has an open vulnerability (CWE-601: URL Redirection to Untrusted Site ('Open Redirect')) affecting @angular/ssr libraries in the npm ecosystem. The issue involves angular ssr has an open redirect via x-forwarded-prefix. Remediation is available by upgrading affected packages to version 21.2.0-rc.1, 21.1.5, 20.3.17, 19.2.21.

CVE-2026-27738 at a Glance

CVE Identifier CVE-2026-27738
GHSA Identifier GHSA-xh43-g2fq-wjrj
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Affected Product @angular/ssr
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-27738

To remediate this vulnerability, upgrade all affected @angular/ssr dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@angular/ssr fixed: 21.2.0-rc.1
npm install @angular/ssr@21.2.0-rc.1
@angular/ssr fixed: 21.1.5
npm install @angular/ssr@21.1.5
@angular/ssr fixed: 20.3.17
npm install @angular/ssr@20.3.17
@angular/ssr fixed: 19.2.21
npm install @angular/ssr@19.2.21
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @angular/ssr

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-27738, inspect your project dependencies using npm:

npm ls @angular/ssr

Analyze the terminal output to locate any version of @angular/ssr in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 21.2.0-rc.1), your application is affected.

Note: The npm ls @angular/ssr command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-601: URL Redirection to Untrusted Site ('Open Redirect'), where the web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect. In @angular/ssr, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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 their`server.ts` before the Angular engine processes the request: ```ts 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 - [Report](https://github.com/angular/angular-cli/issues/32501) - [Fix](https://github.com/angular/angular-cli/pull/32521)

CVE-2026-27738 Affected @angular/ssr Versions

4 component(s)
Fixed Versions:
21.2.0-rc.121.1.520.3.1719.2.21
Product / Package Ecosystem Affected Versions Fixed Version
@angular/ssr
npm
≥ 21.2.0-next.0
< 21.2.0-rc.1
21.2.0-rc.1
@angular/ssr
npm
≥ 21.0.0-next.0
< 21.1.5
21.1.5
@angular/ssr
npm
≥ 20.0.0-next.0
< 20.3.17
20.3.17
@angular/ssr
npm
≥ 19.0.0-next.0
< 19.2.21
19.2.21

References

Frequently Asked Questions

What is CVE-2026-27738?
CVE-2026-27738 is a security vulnerability in @angular/ssr involving Angular SSR has an Open Redirect via X-Forwarded-Prefix under CWE-601: URL Redirection to Untrusted Site ('Open Redirect').
Which @angular/ssr versions are affected?
Affected versions include releases prior to 21.2.0-rc.1, 21.1.5, 20.3.17, 19.2.21 across affected packages: @angular/ssr.
What version fixes CVE-2026-27738?
Upgrading to 21.2.0-rc.1, 21.1.5, 20.3.17, 19.2.21 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @angular/ssr affected?
Yes, @angular/ssr is affected in releases prior to 21.2.0-rc.1, 21.1.5, 20.3.17, 19.2.21. Upgrade your dependency to 21.2.0-rc.1, 21.1.5, 20.3.17, 19.2.21 or later.
What CWE is associated with CVE-2026-27738?
CVE-2026-27738 is classified under CWE-601: URL Redirection to Untrusted Site ('Open Redirect') (The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.).
How can I check npm dependencies for CVE-2026-27738?
Run the dependency tree command: 'npm ls @angular/ssr'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xh43-g2fq-wjrj",
  "modified" : "2026-02-25T22:41:57Z",
  "published" : "2026-02-25T22:41:57Z",
  "aliases" : [ "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.\n\nWhen 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`).\n\n1. The application processes a redirect (e.g., from a router `redirectTo` or i18n locale switch).\n2. Angular receives `///evil.com` as the prefix.\n3. It strips one slash, leaving `//evil.com`.\n4. The resulting string is used in the `Location` header.\n5. Modern browsers interpret `//` as a protocol-relative URL, redirecting the user from `https://your-app.com` to `https://evil.com`.\n\n\n### Impact\nThis vulnerability allows attackers to conduct large-scale phishing and SEO hijacking:\n- **Scale:** A single request can poison a high-traffic route, impacting all users until the cache expires.\n- **SEO Poisoning:** Search engine crawlers may follow and index these malicious redirects, causing the legitimate site to be delisted or associated with malicious domains.\n- **Trust:** Because the initial URL belongs to the trusted domain, users and security tools are less likely to flag the redirect as malicious.\n\n### Attack Preconditions\n\n- The application must use Angular SSR.\n- The application must have routes that perform internal redirects.\n- The infrastructure (Reverse Proxy/CDN) must pass the `X-Forwarded-Prefix` header to the SSR process without sanitization.\n- The cache must not vary on the `X-Forwarded-Prefix` header.\n\n### Patches\n- 21.2.0-rc.1\n- 21.1.5\n- 20.3.17\n- 19.2.21\n\n### Workarounds\nUntil the patch is applied, developers should sanitize the `X-Forwarded-Prefix` header in their`server.ts` before the Angular engine processes the request:\n\n```ts\napp.use((req, res, next) => {\n  const prefix = req.headers['x-forwarded-prefix']?.trim();\n  if (prefix) {\n    // Sanitize by removing all leading slashes\n    req.headers['x-forwarded-prefix'] = prefix.replace(/^[/\\\\]+/, '/');\n  }\n  next();\n});\n\n```\n\n### Resources\n- [Report](https://github.com/angular/angular-cli/issues/32501)\n- [Fix](https://github.com/angular/angular-cli/pull/32521)",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/ssr"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "21.2.0-next.0"
      }, {
        "fixed" : "21.2.0-rc.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "< 21.2.0-rc.0"
    }
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/ssr"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "21.0.0-next.0"
      }, {
        "fixed" : "21.1.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/ssr"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "20.0.0-next.0"
      }, {
        "fixed" : "20.3.17"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/ssr"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "19.0.0-next.0"
      }, {
        "fixed" : "19.2.21"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular-cli/security/advisories/GHSA-xh43-g2fq-wjrj"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-27738"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular-cli/issues/32501"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular-cli/pull/32521"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular-cli/commit/f086eccc36d10cf01c426e35864bc32e1e292323"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/angular/angular-cli"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-601" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-25T22:41:57Z",
    "nvd_published_at" : "2026-02-25T17:25:40Z"
  }
}