Server-side Request Forgery (SSRF) Affecting @angular/ssr package, versions >=19.0.0-next.0 <19.2.18>=20.0.0-next.0 <20.3.6>=21.0.0-next.0 <21.0.0-next.8
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-ANGULARSSR-13635722
- published19 Oct 2025
- disclosed16 Oct 2025
- creditmeDavidNS
Introduced: 16 Oct 2025
NewCVE-2025-62427 (opens in a new tab)How to fix?
Upgrade @angular/ssr to version 19.2.18, 20.3.6, 21.0.0-next.8 or higher.
Overview
@angular/ssr is a the Angular server side rendering utilities.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the createRequestUrl function. An attacker can cause the server to make arbitrary HTTP requests to external domains by supplying a specially crafted request path that begins with double forward slashes or backslashes, which manipulates the URL resolution process and results in subsequent server-side HTTP requests being directed to attacker-controlled endpoints.