---
id: CVE-2025-62427
title: The Angular SSR is a server-rise rendering tool for Angular applications
summary: >-
  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…
severity: none
cwe:
  - CWE-918
published: '2025-10-16'
updated: '2026-10-09'
sourceUpdated: '2026-10-09T10:10:00.193'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-62427'
references:
  - url: >-
      https://github.com/angular/angular-cli/commit/5271547c80662de10cb3bcb648779a83f6efedfb
    label: security-advisories@github.com
  - url: >-
      https://github.com/angular/angular-cli/security/advisories/GHSA-q63q-pgmf-mxhr
    label: security-advisories@github.com
tags:
  - nvd
epss: 0.00432
epssPercentile: 0.35388
ingestedAt: '2026-10-09T12:53:29.105Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.