CVE-2026-27739: Angular SSR is vulnerable to SSRF and Header Injection via request handling pipeline
angular · angular-cli
Affected: angular-cli · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 46% of scored CVEs
DescriptionCVE.org
The Angular SSR is a server-rise rendering tool for Angular applications. Versions prior to 21.2.0-rc.1, 21.1.5, 20.3.17, and 19.2.21 have a Server-Side Request Forgery (SSRF) vulnerability in the Angular SSR request handling pipeline. The vulnerability exists because Angular’s internal URL reconstruction logic directly trusts and consumes user-controlled HTTP headers specifically the Host and `X-Forwarded-*` family to determine the application's base origin without any validation of the destination domain. Specifically, the framework didn't have checks for the host domain, path and character sanitization, and port validation. This vulnerability manifests in two primary ways: implicit relative URL resolution and explicit manual construction. When successfully exploited, this vulnerability allows for arbitrary internal request steering. This can lead to credential exfiltration, internal network probing, and a confidentiality breach. In order to be vulnerable, the victim application must use Angular SSR (Server-Side Rendering), the application must perform `HttpClient` requests using relative URLs OR manually construct URLs using the unvalidated `Host` / `X-Forwarded-*` headers using the `REQUEST` object, the application server must be reachable by an attacker who can influence these headers without strict validation from a front-facing proxy, and the infrastructure (Cloud, CDN, or Load Balancer) must not sanitize or validate incoming headers. Versions 21.2.0-rc.1, 21.1.5, 20.3.17, and 19.2.21 contain a patch. Some workarounds are available. Avoid using `req.headers` for URL construction. Instead, use trusted variables for base API paths. Those who cannot upgrade immediately should implement a middleware in their `server.ts` to enforce numeric ports and validated hostnames.
Affected products3
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- angular · angular-cli>= 21.2.0-next.2, < 21.2.0-rc.0; >= 21.0.0-next.0, < 21.1.5; >= 20.0.0-next.0, < 20.3.17; < 19.2.21
- angular · @nguniversal/common<= 16.2.0
- angular · @nguniversal/express-engine<= 16.2.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Server-Side Request Forgery
- Vendor
- angular
- Published
- February 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-27739 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-918cwe.mitre.org
- github.com/angular/angular-cli/security/advisories/GHSA-x288-377github.com
- github.com/angular/angular-cli/pull/32516github.com
- angular.dev/best-practices/security#preventing-server-side-requeangular.dev
- developer.mozilla.org/en-US/docs/Web/Security/Attacks/SSRFdeveloper.mozilla.org