VulnerabilityPublished 16 Oct 2025

CVE-2025-62427: angular-cli · Server-Side Request Forgery (SSRF)

Affects angular-cliSource CVE Database V5

Not known to be exploited · CVSS 8.7 High : upgrade to 20.3.6 or 19.2.18 soon.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score

8.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 20.3.6, 19.2.18

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade @angular/ssr to 20.3.6 or 19.2.18.

Affected software

Product	Affected	Fixed in
npm@angular/ssr`pkg:npm/@angular/ssr`Other threats	Affected <19.2.18 <20.3.6 =21.0.0-next.8	Fixed in 19.2.18 20.3.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade Angular SSR packages to versions 19.2.18, 20.3.6, 21.0.0-next.8, or later, where the vulnerability is fixed. Organizations should audit their Angular SSR implementations to ensure no untrusted input can influence URL paths starting with // or \\. Implement strict input validation and sanitization on incoming request URLs to prevent schema-relative URL injection. Additionally, configure network egress controls to restrict SSR server outbound HTTP requests to only trusted domains and internal services, limiting the impact of potential SSRF exploitation. Employ runtime monitoring and logging to detect unusual outbound requests originating from SSR processes. Consider using Web Application Firewalls (WAFs) with SSRF detection capabilities to block suspicious requests. Finally, conduct security testing focused on SSRF scenarios in Angular SSR environments to identify and remediate any residual risks.

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.

Impact

For European organizations, this SSRF vulnerability poses significant risks, particularly for those deploying Angular SSR in production environments. Exploitation can lead to unauthorized internal network access, data leakage, or interaction with internal services not intended to be exposed externally. This can compromise confidentiality and integrity of sensitive data and potentially disrupt availability if the attacker leverages the SSRF to perform denial-of-service attacks on internal resources. Organizations relying on Angular SSR for rendering dynamic content on their websites or applications may inadvertently expose backend services or cloud metadata endpoints. Given the widespread use of Angular in Europe’s web development ecosystem, especially in sectors like finance, government, and e-commerce, the impact could be substantial. Attackers could exploit this vulnerability to pivot into internal networks or exfiltrate sensitive information, increasing the risk of data breaches and regulatory non-compliance under GDPR.

Summary

CVE-2025-62427 is a Server-Side Request Forgery (SSRF) vulnerability identified in Angular's Server-Side Rendering (SSR) package (@angular/ssr) prior to versions 19.2.18, 20.3.6, and 21.0.0-next.8. The vulnerability stems from the createRequestUrl function, which uses the native URL constructor to resolve URLs during SSR. When an incoming request path begins with double forward slashes (//) or backslashes (\\), the URL constructor interprets this as a schema-relative URL, overriding the intended base URL's hostname with an attacker-controlled hostname. This manipulation causes the SSR environment to set the page's virtual location to the attacker's domain. Consequently, any relative HTTP requests made during SSR, such as HttpClient.get('assets/data.json'), are resolved against the malicious domain, forcing the server to communicate with external endpoints controlled by the attacker. This can lead to unauthorized data exfiltration, internal network scanning, or other SSRF-related impacts. The vulnerability requires no authentication or user interaction and can be exploited remotely. It affects Angular CLI versions in the specified ranges and has a CVSS 4.0 score of 8.7, indicating high severity. The flaw has been addressed in the patched versions mentioned, but no known exploits are currently reported in the wild.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Oct 2025, 00:50 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats