# Angular SSR is vulnerable to SSRF and Header Injection via request handling pipeline

Advisory record · `GHSA-x288-3778-4hhx`

- **Identifiers:** `GHSA-x288-3778-4hhx` · `CVE-2026-27739`
- **State:** Confirmed
- **Severity:** CVSS 9.2 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 25 Feb 2026
- **Updated:** 25 Feb 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Feb 2026, 22:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.2: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `@angular/ssr` (npm): affected `>=21.2.0-next.0, <21.2.0-rc.1 || >=21.0.0-next.0, <21.1.5 || >=20.0.0-next.0, <20.3.17 || <19.2.21`; fixed in `21.2.0-rc.1`, `21.1.5`, `20.3.17`, `19.2.21`
- `@nguniversal/common` (npm): affected `<=16.2.0`; no fixed version yet
- `@nguniversal/express-engine` (npm): affected `<=16.2.0`; no fixed version yet

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.2 Critical, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0055, the 46th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 25 Feb 2026. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-x288-3778-4hhx](https://github.com/advisories/GHSA-x288-3778-4hhx)
- [OSV: GHSA-x288-3778-4hhx](https://osv.dev/vulnerability/GHSA-x288-3778-4hhx)
- <https://github.com/angular/angular-cli/security/advisories/GHSA-x288-3778-4hhx>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-27739>
- <https://github.com/angular/angular-cli/pull/32516>
- <https://angular.dev/best-practices/security#preventing-server-side-request-forgery-ssrf>
- <https://developer.mozilla.org/en-US/docs/Web/Security/Attacks/SSRF>
- <https://github.com/angular/angular-cli>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-x288-3778-4hhx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x288-3778-4hhx/>. Everything for agents: <https://agentprime.io/llms.txt>.