Server-side Request Forgery (SSRF) Affecting @angular/platform-server package, versions <19.2.23>=20.0.0-next.0 <20.3.22>=21.0.0-next.0 <21.2.15>=22.0.0-next.0 <22.0.0-rc.2
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 applications- Snyk IDSNYK-JS-ANGULARPLATFORMSERVER-17357205
- published17 Jun 2026
- disclosed15 Jun 2026
- creditUnknown
Introduced: 15 Jun 2026
NewCVE-2026-50168 (opens in a new tab)How to fix?
Upgrade @angular/platform-server to version 19.2.23, 20.3.22, 21.2.15, 22.0.0-rc.2 or higher.
Overview
@angular/platform-server is an Angular - library for using Angular in Node.js
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via a parser differential between the strict WHATWG URL parser used for allowlist validation and the lenient Domino URL parser used to initialize the server emulated DOM. An attacker can redirect server-side outgoing requests to arbitrary external endpoints and potentially inject malicious content into the rendered HTML by sending specially crafted HTTP requests with malformed Host headers or absolute-form request URIs.
Note: This is only exploitable if the application is configured for server-side rendering, reconstructs request URLs from raw client inputs, performs outbound backend API requests using relative paths, and has the allowedHosts option enabled.