{"id":"CVE-2026-27739","aliases":["CLSA-2026-1776645366","CLSA-2026-1776645367","CLSA-2026-1778460307","CLSA-2026-1792163460","CLSA-2026-1792163461","CLSA-2026-1792202606","CLSA-2026-1792248406","CLSA-2026-1792248407","CLSA-2026-1792279521","CLSA-2026-1792279522","CLSA-2026-1792327352","CLSA-2026-1792327353","CLSA-2026-1792339029","CLSA-2026-1792339030","CLSA-2026-1792348145","CLSA-2026-1792348147","CLSA-2026-1792358881","CLSA-2026-1792358883","CLSA-2026-1792364739","CLSA-2026-1792364740","CLSA-2026-1792865280","EUVD-2026-8695","GHSA-x288-3778-4hhx"],"status":"published","title":"Angular SSR is vulnerable to SSRF and Header Injection via request handling pipeline","description":"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.","severity":{"version":"4.0","score":9.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N","level":"critical","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00553,"percentile":0.46646,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":true,"fix_available":true},"cwes":["CWE-918"],"published":"2026-02-25T16:47:29Z","modified":"2026-11-02T19:46:33Z","exploits":[{"source":"pocgithub","id":"Mr-Red-007/CVE-2026-27739-POC","title":"Mr-Red-007/CVE-2026-27739-POC","date":"2026-10-22","url":"https://github.com/Mr-Red-007/CVE-2026-27739-POC"},{"source":"pocgithub","id":"mr-redoo7/CVE-2026-27739-POC","title":"mr-redoo7/CVE-2026-27739-POC","date":"2026-04-08","url":"https://github.com/mr-redoo7/CVE-2026-27739-POC"}],"fixes":[{"ecosystem":"npm","package":"@angular/ssr","fixed_in":["21.2.0-rc.0","21.1.5","20.3.17","19.2.21","21.2.0-rc.1"],"sources":["ghsa","osv"]},{"ecosystem":"TuxCare:npm","package":"@angular-devkit/schematics","fixed_in":["17.3.17-tuxcare.3","18.2.21-tuxcare.2"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@angular/cli","fixed_in":["17.3.17-tuxcare.3","18.2.21-tuxcare.2"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@nguniversal/express-engine","fixed_in":["10.1.0-tuxcare.1"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@angular/pwa","fixed_in":["17.3.17-tuxcare.3","18.2.21-tuxcare.2"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@angular/build","fixed_in":["18.2.21-tuxcare.2"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@angular-devkit/build-angular","fixed_in":["17.3.17-tuxcare.3","18.2.21-tuxcare.2"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@angular-devkit/core","fixed_in":["17.3.17-tuxcare.3","18.2.21-tuxcare.2"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@angular-devkit/schematics-cli","fixed_in":["17.3.17-tuxcare.3","18.2.21-tuxcare.2"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@angular/create","fixed_in":["17.3.17-tuxcare.3","18.2.21-tuxcare.2"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@angular/ssr","fixed_in":["17.3.17-tuxcare.3","18.2.21-tuxcare.2"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@ngtools/webpack","fixed_in":["17.3.17-tuxcare.3","18.2.21-tuxcare.2"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@schematics/angular","fixed_in":["17.3.17-tuxcare.3","18.2.21-tuxcare.2"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"@nguniversal/common","fixed_in":["10.1.0-tuxcare.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"@angular/ssr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"21.2.0-next.0"},{"fixed":"21.2.0-rc.0"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@angular/ssr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"21.0.0-next.0"},{"fixed":"21.1.5"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@angular/ssr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"20.0.0-next.0"},{"fixed":"20.3.17"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@angular/ssr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"19.2.21"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@nguniversal/common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"16.2.0"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@nguniversal/express-engine","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"16.2.0"}]}]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular-devkit/schematics","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"17.3.17-tuxcare.0"},{"fixed":"17.3.17-tuxcare.3"}]}],"versions":["17.3.17","17.3.17-tuxcare.1","17.3.17-tuxcare.2"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular/cli","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"17.3.17-tuxcare.0"},{"fixed":"17.3.17-tuxcare.3"}]}],"versions":["17.3.17","17.3.17-tuxcare.1","17.3.17-tuxcare.2"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular-devkit/schematics","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"18.2.21-tuxcare.0"},{"fixed":"18.2.21-tuxcare.2"}]}],"versions":["18.2.21","18.2.21-tuxcare.1"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular/cli","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"18.2.21-tuxcare.0"},{"fixed":"18.2.21-tuxcare.2"}]}],"versions":["18.2.21","18.2.21-tuxcare.1"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@nguniversal/express-engine","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"10.1.0-tuxcare.0"},{"fixed":"10.1.0-tuxcare.1"}]}],"versions":["10.1.0"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular/pwa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"17.3.17-tuxcare.0"},{"fixed":"17.3.17-tuxcare.3"}]}],"versions":["17.3.17","17.3.17-tuxcare.1","17.3.17-tuxcare.2"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular/pwa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"18.2.21-tuxcare.0"},{"fixed":"18.2.21-tuxcare.2"}]}],"versions":["18.2.21","18.2.21-tuxcare.1"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular/build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"18.2.21-tuxcare.0"},{"fixed":"18.2.21-tuxcare.2"}]}],"versions":["18.2.21","18.2.21-tuxcare.1"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular-devkit/build-angular","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"17.3.17-tuxcare.0"},{"fixed":"17.3.17-tuxcare.3"}]}],"versions":["17.3.17"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular-devkit/build-angular","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"18.2.21-tuxcare.0"},{"fixed":"18.2.21-tuxcare.2"}]}],"versions":["18.2.21"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular-devkit/core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"17.3.17-tuxcare.0"},{"fixed":"17.3.17-tuxcare.3"}]}],"versions":["17.3.17"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular-devkit/core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"18.2.21-tuxcare.0"},{"fixed":"18.2.21-tuxcare.2"}]}],"versions":["18.2.21"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular-devkit/schematics-cli","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"17.3.17-tuxcare.0"},{"fixed":"17.3.17-tuxcare.3"}]}],"versions":["17.3.17"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular-devkit/schematics-cli","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"18.2.21-tuxcare.0"},{"fixed":"18.2.21-tuxcare.2"}]}],"versions":["18.2.21"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular/create","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"17.3.17-tuxcare.0"},{"fixed":"17.3.17-tuxcare.3"}]}],"versions":["17.3.17","17.3.17-tuxcare.1","17.3.17-tuxcare.2"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular/create","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"18.2.21-tuxcare.0"},{"fixed":"18.2.21-tuxcare.2"}]}],"versions":["18.2.21","18.2.21-tuxcare.1"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular/ssr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"17.3.17-tuxcare.0"},{"fixed":"17.3.17-tuxcare.3"}]}],"versions":["17.3.17","17.3.17-tuxcare.1","17.3.17-tuxcare.2"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@angular/ssr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"18.2.21-tuxcare.0"},{"fixed":"18.2.21-tuxcare.2"}]}],"versions":["18.2.21","18.2.21-tuxcare.1"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@ngtools/webpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"17.3.17-tuxcare.0"},{"fixed":"17.3.17-tuxcare.3"}]}],"versions":["17.3.17"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@ngtools/webpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"18.2.21-tuxcare.0"},{"fixed":"18.2.21-tuxcare.2"}]}],"versions":["18.2.21"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@schematics/angular","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"17.3.17-tuxcare.0"},{"fixed":"17.3.17-tuxcare.3"}]}],"versions":["17.3.17"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@schematics/angular","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"18.2.21-tuxcare.0"},{"fixed":"18.2.21-tuxcare.2"}]}],"versions":["18.2.21"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"@nguniversal/common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"10.1.0-tuxcare.0"},{"fixed":"10.1.0-tuxcare.1"}]}],"versions":["10.1.0"]},{"source":"osv","ecosystem":"npm","package":"@angular/ssr","ranges":[{"type":"SEMVER","events":[{"introduced":"21.2.0-next.0"},{"fixed":"21.2.0-rc.1"}]}]},{"source":"osv","ecosystem":"npm","package":"@angular/ssr","ranges":[{"type":"SEMVER","events":[{"introduced":"21.0.0-next.0"},{"fixed":"21.1.5"}]}]},{"source":"osv","ecosystem":"npm","package":"@angular/ssr","ranges":[{"type":"SEMVER","events":[{"introduced":"20.0.0-next.0"},{"fixed":"20.3.17"}]}]},{"source":"osv","ecosystem":"npm","package":"@angular/ssr","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"19.2.21"}]}]},{"source":"osv","ecosystem":"npm","package":"@nguniversal/common","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"16.2.0"}]}]},{"source":"osv","ecosystem":"npm","package":"@nguniversal/express-engine","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"16.2.0"}]}]}],"products":[{"vendor":"angular","product":"@nguniversal/common"},{"vendor":"angular","product":"@nguniversal/express-engine"},{"vendor":"angular","product":"angular-cli"}],"references":[{"url":"https://github.com/angular/angular-cli/security/advisories/GHSA-x288-3778-4hhx","tags":["x_refsource_CONFIRM","advisory","web"]},{"url":"https://github.com/angular/angular-cli/pull/32516","tags":["x_refsource_MISC","fix","web"]},{"url":"https://angular.dev/best-practices/security#preventing-server-side-request-forgery-ssrf","tags":["x_refsource_MISC","web"]},{"url":"https://developer.mozilla.org/en-US/docs/Web/Security/Attacks/SSRF","tags":["x_refsource_MISC","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-27739","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-x288-3778-4hhx"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/27xxx/CVE-2026-27739.json","tags":["advisory"]},{"url":"https://github.com/angular/angular-cli","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2026-27739","title":"Angular SSR is vulnerable to SSRF and Header Injection via request handling pipeline","description":"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.","status":"published","published":"2026-02-25T16:47:29.705Z","modified":"2026-02-27T17:59:11.328Z","cvss":[{"version":"4.0","score":9.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N","level":"critical","assessor":"cna"}],"cwes":["CWE-918"],"updated_at":"2026-11-02T14:19:49.199185Z"}],"euvd":[{"id":"EUVD-2026-8695","description":"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.","status":"published","published":"2026-02-25T16:47:29Z","modified":"2026-02-27T17:59:11Z","cvss":[{"version":"4.0","score":9.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N","level":"critical"}],"updated_at":"2026-11-02T19:48:13.609806Z"}],"ghsa":[{"id":"GHSA-x288-3778-4hhx","title":"Angular SSR is vulnerable to SSRF and Header Injection via request handling pipeline","description":"A [Server-Side Request Forgery (SSRF)](https://developer.mozilla.org/en-US/docs/Web/Security/Attacks/SSRF) vulnerability has been identified 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.\n\nSpecifically, the framework didn't have checks for the following:\n- **Host Domain**: The `Host` and `X-Forwarded-Host` headers were not checked to belong to a trusted origin. This allows an attacker to redefine the \"base\" of the application to an arbitrary external domain.\n- **Path \u0026 Character Sanitization**: The `X-Forwarded-Host` header was not checked for path segments or special characters, allowing manipulation of the base path for all resolved relative URLs.\n- **Port Validation**: The `X-Forwarded-Port` header was not verified as numeric, leading to malformed URI construction or injection attacks.\n\n\nThis vulnerability manifests in two primary ways:\n\n- **Implicit Relative URL Resolution**: Angular's `HttpClient` resolves relative URLs against this unvalidated and potentially malformed base origin. An attacker can \"steer\" these requests to an external server or internal service.\n- **Explicit Manual Construction**: Developers injecting the `REQUEST` object to manually construct URLs (for fetch or third-party SDKs) directly inherit these unsanitized values. By accessing the `Host` / `X-Forwarded-*` headers, the application logic may perform requests to attacker-controlled destinations or malformed endpoints.\n\n### Impact\n\nWhen successfully exploited, this vulnerability allows for arbitrary internal request steering. This can lead to:\n- **Credential Exfiltration**: Stealing sensitive `Authorization` headers or session cookies by redirecting them to an attacker's server.\n- **Internal Network Probing**: Accessing and transmitting data from internal services, databases, or cloud metadata endpoints (e.g., `169.254.169.254`) not exposed to the public internet.\n- Confidentiality Breach: Accessing sensitive information processed within the application's server-side context.\n\n### Attack Preconditions\n\n- The victim application must use Angular SSR (Server-Side Rendering).\n- The application must perform `HttpClient` requests using relative URLs OR manually construct URLs using the unvalidated `Host` / `X-Forwarded-*` headers using the `REQUEST` object.\n- **Direct Header Access**: The application server is reachable by an attacker who can influence these headers without strict validation from a front-facing proxy.\n- **Lack of Upstream Validation**: The infrastructure (Cloud, CDN, or Load Balancer) does not sanitize or validate incoming headers.\n\n### Patches\n\n- 21.2.0-rc.1\n- 21.1.5\n- 20.3.17\n- 19.2.21\n\n\n### Workarounds\n- **Use Absolute URLs:** Avoid using `req.headers` for URL construction. Instead, use trusted variables for your base API paths.\n- **Implement Strict Header Validation (Middleware)**: If you cannot upgrade immediately, implement a middleware in your `server.ts` to enforce numeric ports and validated hostnames.\n\n```ts\nconst ALLOWED_HOSTS = new Set(['your-domain.com']);\n\napp.use((req, res, next) =\u003e {\n  const hostHeader = (req.headers['x-forwarded-host'] ?? req.headers['host'])?.toString();\n  const portHeader = req.headers['x-forwarded-port']?.toString();\n\n  if (hostHeader) {\n    const hostname = hostHeader.split(':')[0];\n    // Reject if hostname contains path separators or is not in allowlist\n    if (/^[a-z0-9.:-]+$/i.test(hostname) || \n       (!ALLOWED_HOSTS.has(hostname) \u0026\u0026 hostname !== 'localhost')) {\n      return res.status(400).send('Invalid Hostname');\n    }\n  }\n\n  // Ensure port is strictly numeric if provided\n  if (portHeader \u0026\u0026 !/^\\d+$/.test(portHeader)) {\n    return res.status(400).send('Invalid Port');\n  }\n\n  next();\n});\n```\n\n### References\n\n- [Fix](https://github.com/angular/angular-cli/pull/32516)\n- [Docs](https://angular.dev/best-practices/security#preventing-server-side-request-forgery-ssrf)","status":"published","published":"2026-02-25T22:42:36Z","modified":"2026-02-25T22:42:37Z","cvss":[{"version":"4.0","score":9.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N","level":"critical"}],"cwes":["CWE-918"],"updated_at":"2026-11-02T14:39:27.949248Z"}],"nvd":[{"id":"CVE-2026-27739","description":"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.","status":"published","published":"2026-02-25T18:23:40.8Z","modified":"2026-06-17T10:27:36.443Z","cvss":[{"version":"4.0","score":9.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"critical","assessor":"secondary"}],"cwes":["CWE-918"],"updated_at":"2026-11-02T14:12:07.027269Z"}],"osv":[{"id":"CVE-2026-27739","title":"Angular SSR is vulnerable to SSRF and Header Injection via request handling pipeline","description":"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.","status":"published","published":"2026-02-25T16:47:29.705Z","modified":"2026-10-28T02:31:13.520728323Z","cvss":[{"version":"4.0","score":9.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N","level":"critical"}],"cwes":["CWE-918"],"updated_at":"2026-11-02T15:45:00.180685Z"},{"id":"GHSA-x288-3778-4hhx","title":"Angular SSR is vulnerable to SSRF and Header Injection via request handling pipeline","description":"A [Server-Side Request Forgery (SSRF)](https://developer.mozilla.org/en-US/docs/Web/Security/Attacks/SSRF) vulnerability has been identified 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.\n\nSpecifically, the framework didn't have checks for the following:\n- **Host Domain**: The `Host` and `X-Forwarded-Host` headers were not checked to belong to a trusted origin. This allows an attacker to redefine the \"base\" of the application to an arbitrary external domain.\n- **Path \u0026 Character Sanitization**: The `X-Forwarded-Host` header was not checked for path segments or special characters, allowing manipulation of the base path for all resolved relative URLs.\n- **Port Validation**: The `X-Forwarded-Port` header was not verified as numeric, leading to malformed URI construction or injection attacks.\n\n\nThis vulnerability manifests in two primary ways:\n\n- **Implicit Relative URL Resolution**: Angular's `HttpClient` resolves relative URLs against this unvalidated and potentially malformed base origin. An attacker can \"steer\" these requests to an external server or internal service.\n- **Explicit Manual Construction**: Developers injecting the `REQUEST` object to manually construct URLs (for fetch or third-party SDKs) directly inherit these unsanitized values. By accessing the `Host` / `X-Forwarded-*` headers, the application logic may perform requests to attacker-controlled destinations or malformed endpoints.\n\n### Impact\n\nWhen successfully exploited, this vulnerability allows for arbitrary internal request steering. This can lead to:\n- **Credential Exfiltration**: Stealing sensitive `Authorization` headers or session cookies by redirecting them to an attacker's server.\n- **Internal Network Probing**: Accessing and transmitting data from internal services, databases, or cloud metadata endpoints (e.g., `169.254.169.254`) not exposed to the public internet.\n- Confidentiality Breach: Accessing sensitive information processed within the application's server-side context.\n\n### Attack Preconditions\n\n- The victim application must use Angular SSR (Server-Side Rendering).\n- The application must perform `HttpClient` requests using relative URLs OR manually construct URLs using the unvalidated `Host` / `X-Forwarded-*` headers using the `REQUEST` object.\n- **Direct Header Access**: The application server is reachable by an attacker who can influence these headers without strict validation from a front-facing proxy.\n- **Lack of Upstream Validation**: The infrastructure (Cloud, CDN, or Load Balancer) does not sanitize or validate incoming headers.\n\n### Patches\n\n- 21.2.0-rc.1\n- 21.1.5\n- 20.3.17\n- 19.2.21\n\n\n### Workarounds\n- **Use Absolute URLs:** Avoid using `req.headers` for URL construction. Instead, use trusted variables for your base API paths.\n- **Implement Strict Header Validation (Middleware)**: If you cannot upgrade immediately, implement a middleware in your `server.ts` to enforce numeric ports and validated hostnames.\n\n```ts\nconst ALLOWED_HOSTS = new Set(['your-domain.com']);\n\napp.use((req, res, next) =\u003e {\n  const hostHeader = (req.headers['x-forwarded-host'] ?? req.headers['host'])?.toString();\n  const portHeader = req.headers['x-forwarded-port']?.toString();\n\n  if (hostHeader) {\n    const hostname = hostHeader.split(':')[0];\n    // Reject if hostname contains path separators or is not in allowlist\n    if (/^[a-z0-9.:-]+$/i.test(hostname) || \n       (!ALLOWED_HOSTS.has(hostname) \u0026\u0026 hostname !== 'localhost')) {\n      return res.status(400).send('Invalid Hostname');\n    }\n  }\n\n  // Ensure port is strictly numeric if provided\n  if (portHeader \u0026\u0026 !/^\\d+$/.test(portHeader)) {\n    return res.status(400).send('Invalid Port');\n  }\n\n  next();\n});\n```\n\n### References\n\n- [Fix](https://github.com/angular/angular-cli/pull/32516)\n- [Docs](https://angular.dev/best-practices/security#preventing-server-side-request-forgery-ssrf)","status":"published","published":"2026-02-25T22:42:36Z","modified":"2026-02-25T22:47:57.558366Z","cvss":[{"version":"4.0","score":9.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N","level":"critical"}],"cwes":["CWE-918"],"updated_at":"2026-11-02T15:46:59.131095Z"},{"id":"CLSA-2026-1776645366","title":"TuxCare security update for 2 packages (1 CVE)","description":"TuxCare rebuilt 2 packages to address 1 CVE. Fixed in 17.3.17-tuxcare.3.","status":"published","published":"2026-08-04T14:52:27Z","modified":"2026-10-19T07:45:07.032128157Z","updated_at":"2026-11-02T15:43:44.009773Z"},{"id":"CLSA-2026-1776645367","title":"TuxCare security update for 2 packages (1 CVE)","description":"TuxCare rebuilt 2 packages to address 1 CVE. Fixed in 18.2.21-tuxcare.2.","status":"published","published":"2026-08-04T14:52:27Z","modified":"2026-10-19T07:45:10.591212428Z","updated_at":"2026-11-02T15:43:44.009773Z"},{"id":"CLSA-2026-1778460307","title":"TuxCare security update for @nguniversal/express-engine (1 CVE)","description":"TuxCare rebuilt @nguniversal/express-engine to address 1 CVE. Fixed in 10.1.0-tuxcare.1.","status":"published","published":"2026-08-04T14:52:31Z","modified":"2026-11-02T19:46:33.995550728Z","updated_at":"2026-11-02T20:28:42.34712Z"},{"id":"CLSA-2026-1792163460","title":"TuxCare security update for @angular/pwa (1 CVE)","description":"TuxCare rebuilt @angular/pwa to address 1 CVE. Fixed in 17.3.17-tuxcare.3.","status":"published","published":"2026-10-16T15:10:59Z","modified":"2026-10-16T16:31:40.46540172Z","updated_at":"2026-11-02T15:43:51.466048Z"},{"id":"CLSA-2026-1792163461","title":"TuxCare security update for @angular/pwa (1 CVE)","description":"TuxCare rebuilt @angular/pwa to address 1 CVE. Fixed in 18.2.21-tuxcare.2.","status":"published","published":"2026-10-16T15:11:00Z","modified":"2026-10-16T16:31:40.456858451Z","updated_at":"2026-11-02T15:43:51.466048Z"},{"id":"CLSA-2026-1792202606","title":"TuxCare security update for @angular/build (1 CVE)","description":"TuxCare rebuilt @angular/build to address 1 CVE. Fixed in 18.2.21-tuxcare.2.","status":"published","published":"2026-10-17T02:03:26Z","modified":"2026-10-17T07:00:35.123856785Z","updated_at":"2026-11-02T15:43:51.747192Z"},{"id":"CLSA-2026-1792248406","title":"TuxCare security update for @angular-devkit/build-angular (1 CVE)","description":"TuxCare rebuilt @angular-devkit/build-angular to address 1 CVE. Fixed in 17.3.17-tuxcare.3.","status":"published","published":"2026-10-17T14:46:46Z","modified":"2026-10-17T19:01:11.154285132Z","updated_at":"2026-11-02T15:43:52.011757Z"},{"id":"CLSA-2026-1792248407","title":"TuxCare security update for @angular-devkit/build-angular (1 CVE)","description":"TuxCare rebuilt @angular-devkit/build-angular to address 1 CVE. Fixed in 18.2.21-tuxcare.2.","status":"published","published":"2026-10-17T14:46:46Z","modified":"2026-10-17T19:01:10.65935332Z","updated_at":"2026-11-02T15:43:52.011757Z"},{"id":"CLSA-2026-1792279521","title":"TuxCare security update for @angular-devkit/core (1 CVE)","description":"TuxCare rebuilt @angular-devkit/core to address 1 CVE. Fixed in 17.3.17-tuxcare.3.","status":"published","published":"2026-10-17T23:25:21Z","modified":"2026-10-18T01:30:45.060153896Z","updated_at":"2026-11-02T15:43:52.288832Z"},{"id":"CLSA-2026-1792279522","title":"TuxCare security update for @angular-devkit/core (1 CVE)","description":"TuxCare rebuilt @angular-devkit/core to address 1 CVE. Fixed in 18.2.21-tuxcare.2.","status":"published","published":"2026-10-17T23:25:21Z","modified":"2026-10-18T01:30:41.611112023Z","updated_at":"2026-11-02T15:43:52.288832Z"},{"id":"CLSA-2026-1792327352","title":"TuxCare security update for @angular-devkit/schematics-cli (1 CVE)","description":"TuxCare rebuilt @angular-devkit/schematics-cli to address 1 CVE. Fixed in 17.3.17-tuxcare.3.","status":"published","published":"2026-10-18T12:42:32Z","modified":"2026-10-18T19:15:39.944144951Z","updated_at":"2026-11-02T15:43:52.545698Z"},{"id":"CLSA-2026-1792327353","title":"TuxCare security update for @angular-devkit/schematics-cli (1 CVE)","description":"TuxCare rebuilt @angular-devkit/schematics-cli to address 1 CVE. Fixed in 18.2.21-tuxcare.2.","status":"published","published":"2026-10-18T12:42:33Z","modified":"2026-10-18T19:15:38.043384149Z","updated_at":"2026-11-02T15:43:52.545698Z"},{"id":"CLSA-2026-1792339029","title":"TuxCare security update for @angular/create (1 CVE)","description":"TuxCare rebuilt @angular/create to address 1 CVE. Fixed in 17.3.17-tuxcare.3.","status":"published","published":"2026-10-18T15:57:09Z","modified":"2026-10-18T19:15:44.113991774Z","updated_at":"2026-11-02T15:43:52.545698Z"},{"id":"CLSA-2026-1792339030","title":"TuxCare security update for @angular/create (1 CVE)","description":"TuxCare rebuilt @angular/create to address 1 CVE. Fixed in 18.2.21-tuxcare.2.","status":"published","published":"2026-10-18T15:57:09Z","modified":"2026-10-18T19:15:44.108577652Z","updated_at":"2026-11-02T15:43:52.545698Z"},{"id":"CLSA-2026-1792348145","title":"TuxCare security update for @angular/ssr (1 CVE)","description":"TuxCare rebuilt @angular/ssr to address 1 CVE. Fixed in 17.3.17-tuxcare.3.","status":"published","published":"2026-10-18T18:29:05Z","modified":"2026-10-18T19:16:05.458288596Z","updated_at":"2026-11-02T15:43:52.782414Z"},{"id":"CLSA-2026-1792348147","title":"TuxCare security update for @angular/ssr (1 CVE)","description":"TuxCare rebuilt @angular/ssr to address 1 CVE. Fixed in 18.2.21-tuxcare.2.","status":"published","published":"2026-10-18T18:29:07Z","modified":"2026-10-18T19:16:05.446324484Z","updated_at":"2026-11-02T15:43:52.782414Z"},{"id":"CLSA-2026-1792358881","title":"TuxCare security update for @ngtools/webpack (1 CVE)","description":"TuxCare rebuilt @ngtools/webpack to address 1 CVE. Fixed in 17.3.17-tuxcare.3.","status":"published","published":"2026-10-18T21:28:01Z","modified":"2026-10-19T07:46:01.18437156Z","updated_at":"2026-11-02T15:43:53.071325Z"},{"id":"CLSA-2026-1792358883","title":"TuxCare security update for @ngtools/webpack (1 CVE)","description":"TuxCare rebuilt @ngtools/webpack to address 1 CVE. Fixed in 18.2.21-tuxcare.2.","status":"published","published":"2026-10-18T21:28:02Z","modified":"2026-10-19T07:46:00.97986769Z","updated_at":"2026-11-02T15:43:53.071325Z"},{"id":"CLSA-2026-1792364739","title":"TuxCare security update for @schematics/angular (1 CVE)","description":"TuxCare rebuilt @schematics/angular to address 1 CVE. Fixed in 17.3.17-tuxcare.3.","status":"published","published":"2026-10-18T23:05:39Z","modified":"2026-10-19T07:46:06.688932291Z","updated_at":"2026-11-02T15:43:53.071325Z"},{"id":"CLSA-2026-1792364740","title":"TuxCare security update for @schematics/angular (1 CVE)","description":"TuxCare rebuilt @schematics/angular to address 1 CVE. Fixed in 18.2.21-tuxcare.2.","status":"published","published":"2026-10-18T23:05:40Z","modified":"2026-10-19T07:46:05.849075424Z","updated_at":"2026-11-02T15:43:53.071325Z"},{"id":"CLSA-2026-1792865280","title":"TuxCare security update for @nguniversal/common (1 CVE)","description":"TuxCare rebuilt @nguniversal/common to address 1 CVE. Fixed in 10.1.0-tuxcare.1.","status":"published","published":"2026-10-24T18:08:00Z","modified":"2026-10-24T19:15:02.425697105Z","updated_at":"2026-11-02T15:43:54.981307Z"}]}}