CVE-2026-27738

The Angular SSR is a server-rise rendering tool for Angular applications. An Open Redirect vulnerability exists in the internal URL processing logic in versions on the 19.x branch prior to 19.2.21, the 20.x branch prior to 20.3.17, and the 21.x branch prior to 21.1.5 and 21.2.0-rc.1. 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. This vulnerability allows attackers to conduct large-scale phishing and SEO hijacking. In order to be vulnerable, 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, and the cache must not vary on the `X-Forwarded-Prefix` header. Versions 21.2.0-rc.1, 21.1.5, 20.3.17, and 19.2.21 contain a patch. Until the patch is applied, developers should sanitize the `X-Forwarded-Prefix` header in their`server.ts` before the Angular engine processes the request.

Published Feb 26, 2026

https://github.com/advisories/GHSA-xh43-g2fq-wjrj

CVSS ScoreMedium

6.9

Ecosystem	Package	Version

Ecosystem	Package	Version

Vulnerabilities

CVE-2026-27738

The Angular SSR is a server-rise rendering tool for Angular applications. An Open Redirect vulnerability exists in the internal URL processing logic in versions on the 19.x branch prior to 19.2.21, the 20.x branch prior to 20.3.17, and the 21.x branch prior to 21.1.5 and 21.2.0-rc.1. 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. This vulnerability allows attackers to conduct large-scale phishing and SEO hijacking. In order to be vulnerable, 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, and the cache must not vary on the `X-Forwarded-Prefix` header. Versions 21.2.0-rc.1, 21.1.5, 20.3.17, and 19.2.21 contain a patch. Until the patch is applied, developers should sanitize the `X-Forwarded-Prefix` header in their`server.ts` before the Angular engine processes the request.

Published Feb 26, 2026

https://github.com/advisories/GHSA-xh43-g2fq-wjrj

CVSS ScoreMedium

6.9


npm	@angular/ssr	19.0.0-next.0
npm	@angular/ssr	19.0.0-next.10
npm	@angular/ssr	19.0.0-next.11
npm	@angular/ssr	19.0.0-next.12
npm	@angular/ssr	19.0.0-next.13
npm	@angular/ssr	19.0.0-next.1
npm	@angular/ssr	19.0.0-next.2
npm	@angular/ssr	19.0.0-next.3
npm	@angular/ssr	19.0.0-next.4
npm	@angular/ssr	19.0.0-next.5
npm	@angular/ssr	19.0.0-next.6
npm	@angular/ssr	19.0.0-next.7
npm	@angular/ssr	19.0.0-next.8
npm	@angular/ssr	19.0.0-next.9
npm	@angular/ssr	19.0.0-rc.0
npm	@angular/ssr	19.0.0-rc.1
npm	@angular/ssr	19.0.0-rc.2
npm	@angular/ssr	19.0.0-rc.3
npm	@angular/ssr	19.0.0
npm	@angular/ssr	19.0.1
npm	@angular/ssr	19.0.2
npm	@angular/ssr	19.0.3
npm	@angular/ssr	19.0.4
npm	@angular/ssr	19.0.5
npm	@angular/ssr	19.0.6
npm	@angular/ssr	19.0.7
npm	@angular/ssr	19.1.0-next.0
npm	@angular/ssr	19.1.0-next.1
npm	@angular/ssr	19.1.0-next.2
npm	@angular/ssr	19.1.0-rc.0
npm	@angular/ssr	19.1.0
npm	@angular/ssr	19.1.1
npm	@angular/ssr	19.1.2
npm	@angular/ssr	19.1.3
npm	@angular/ssr	19.1.4
npm	@angular/ssr	19.1.5
npm	@angular/ssr	19.1.6
npm	@angular/ssr	19.1.7
npm	@angular/ssr	19.1.8
npm	@angular/ssr	19.1.9
npm	@angular/ssr	19.2.0-next.0
npm	@angular/ssr	19.2.0-next.1
npm	@angular/ssr	19.2.0-next.2
npm	@angular/ssr	19.2.0-rc.0
npm	@angular/ssr	19.2.0
npm	@angular/ssr	19.2.10
npm	@angular/ssr	19.2.11
npm	@angular/ssr	19.2.12
npm	@angular/ssr	19.2.13
npm	@angular/ssr	19.2.14

Ecosystem	Package	Version


npm	@angular/ssr	19.0.0-next.0
npm	@angular/ssr	19.0.0-next.10
npm	@angular/ssr	19.0.0-next.11
npm	@angular/ssr	19.0.0-next.12
npm	@angular/ssr	19.0.0-next.13
npm	@angular/ssr	19.0.0-next.1
npm	@angular/ssr	19.0.0-next.2
npm	@angular/ssr	19.0.0-next.3
npm	@angular/ssr	19.0.0-next.4
npm	@angular/ssr	19.0.0-next.5
npm	@angular/ssr	19.0.0-next.6
npm	@angular/ssr	19.0.0-next.7
npm	@angular/ssr	19.0.0-next.8
npm	@angular/ssr	19.0.0-next.9
npm	@angular/ssr	19.0.0-rc.0
npm	@angular/ssr	19.0.0-rc.1
npm	@angular/ssr	19.0.0-rc.2
npm	@angular/ssr	19.0.0-rc.3
npm	@angular/ssr	19.0.0
npm	@angular/ssr	19.0.1
npm	@angular/ssr	19.0.2
npm	@angular/ssr	19.0.3
npm	@angular/ssr	19.0.4
npm	@angular/ssr	19.0.5
npm	@angular/ssr	19.0.6
npm	@angular/ssr	19.0.7
npm	@angular/ssr	19.1.0-next.0
npm	@angular/ssr	19.1.0-next.1
npm	@angular/ssr	19.1.0-next.2
npm	@angular/ssr	19.1.0-rc.0
npm	@angular/ssr	19.1.0
npm	@angular/ssr	19.1.1
npm	@angular/ssr	19.1.2
npm	@angular/ssr	19.1.3
npm	@angular/ssr	19.1.4
npm	@angular/ssr	19.1.5
npm	@angular/ssr	19.1.6
npm	@angular/ssr	19.1.7
npm	@angular/ssr	19.1.8
npm	@angular/ssr	19.1.9
npm	@angular/ssr	19.2.0-next.0
npm	@angular/ssr	19.2.0-next.1
npm	@angular/ssr	19.2.0-next.2
npm	@angular/ssr	19.2.0-rc.0
npm	@angular/ssr	19.2.0
npm	@angular/ssr	19.2.10
npm	@angular/ssr	19.2.11
npm	@angular/ssr	19.2.12
npm	@angular/ssr	19.2.13
npm	@angular/ssr	19.2.14

Find vulnerabilities. Fix fast with AI.

CVE-2026-27738

CVE-2026-27738