CVE-2026-46417: @angular/platform-server SSRF Vulnerability
HIGHCVE-2026-46417 is a HIGH (CVSS 6.1) ssrf vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting @angular/platform-server libraries in the npm ecosystem. The issue involves ssrf via hostname hijacking. Remediation is available by upgrading affected packages to version 22.0.0-next.12, 21.2.13, 20.3.21, 19.2.22.
CVE-2026-46417 at a Glance
Security Impact
CVSS: 6.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).
How to Fix CVE-2026-46417
To remediate this vulnerability, upgrade all affected @angular/platform-server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @angular/platform-server@22.0.0-next.12
npm install @angular/platform-server@21.2.13
npm install @angular/platform-server@20.3.21
npm install @angular/platform-server@19.2.22
npm install @angular/platform-server@Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @angular/platform-server
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-46417, inspect your project dependencies using npm:
npm ls @angular/platform-server
Analyze the terminal output to locate any version of @angular/platform-server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 22.0.0-next.12), your application is affected.
Note: The npm ls @angular/platform-server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where 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. In @angular/platform-server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-46417 Affected @angular/platform-server Versions
5 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@angular/platform-server
|
npm |
≥ 22.0.0-next.0
< 22.0.0-next.12
|
22.0.0-next.12
|
|
@angular/platform-server
|
npm |
≥ 21.0.0-next.0
< 21.2.13
|
21.2.13
|
|
@angular/platform-server
|
npm |
≥ 20.0.0-next.0
< 20.3.21
|
20.3.21
|
|
@angular/platform-server
|
npm |
≥ 19.0.0-next.0
< 19.2.22
|
19.2.22
|
|
@angular/platform-server
|
npm |
≤ 18.2.14
|
|
References
Frequently Asked Questions
What is CVE-2026-46417?
Which @angular/platform-server versions are affected?
What version fixes CVE-2026-46417?
Is @angular/platform-server affected?
What is the CVSS score of CVE-2026-46417?
What CWE is associated with CVE-2026-46417?
How can I check npm dependencies for CVE-2026-46417?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-rfh7-fxqc-q52v",
"modified" : "2026-07-15T22:04:40Z",
"published" : "2026-05-19T20:29:49Z",
"aliases" : [ "CVE-2026-46417" ],
"summary" : "@angular/platform-server: SSRF via Hostname Hijacking",
"details" : "### Impact\n\nA Server-Side Request Forgery (SSRF) vulnerability exists in `@angular/platform-server`. The issue stems from how the server-side rendering (SSR) engine processes the request URL provided to the rendering entry points.\n\nWhen an absolute-form URL (e.g., `http://evil.com`) is passed to the rendering engine, the internal `ServerPlatformLocation` can be manipulated into adopting the attacker-controlled domain as the \"current\" hostname.\n\nConsequently, any relative `HttpClient` requests or `PlatformLocation.hostname` references are redirected to the attacker controlled server, potentially exposing internal APIs or metadata services.\n\n### Fix Information\nThe vulnerability is mitigated by introducing an Allowlist Mechanism directly into the core rendering APIs.\nThe renderModule and renderApplication functions now include an allowedHosts configuration option. The rendering engine validates the hostname extracted from the request URL against this list before proceeding. If the hostname does not match an allowed entry, the engine prevents the hostname hijacking, ensuring that HttpClient requests remain restricted to trusted domains.\n\n\n### Patches\n- 22.0.0-next.12\n- 21.2.13\n- 20.3.21\n- 19.2.22\n\n\n### Workarounds\nDevelopers unable to update immediately should implement strict URL validation in their server entry point (e.g., `server.ts`). Ensure that `req.url` is validated against a known list of trusted hostnames or normalized to a relative path before being passed to`renderApplication` or `renderModule`.\n\n```TypeScript\n// Example manual normalization in Express\napp.get('*', (req, res, next) => {\n const trustedHost = 'localhost:4000';\n // Ensure the request target matches expectations\n if (req.headers.host !== trustedHost) {\n return res.status(403).send('Forbidden');\n }\n next();\n});\n```",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N"
}, {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@angular/platform-server"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "22.0.0-next.0"
}, {
"fixed" : "22.0.0-next.12"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@angular/platform-server"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "21.0.0-next.0"
}, {
"fixed" : "21.2.13"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@angular/platform-server"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "20.0.0-next.0"
}, {
"fixed" : "20.3.21"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@angular/platform-server"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "19.0.0-next.0"
}, {
"fixed" : "19.2.22"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@angular/platform-server"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "18.2.14"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/angular/angular/security/advisories/GHSA-rfh7-fxqc-q52v"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-46417"
}, {
"type" : "WEB",
"url" : "https://github.com/angular/angular/pull/68570"
}, {
"type" : "WEB",
"url" : "https://access.redhat.com/security/cve/CVE-2026-46417"
}, {
"type" : "WEB",
"url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2491444"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/angular/angular"
}, {
"type" : "WEB",
"url" : "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-46417.json"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-918" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-19T20:29:49Z",
"nvd_published_at" : "2026-06-22T18:16:38Z"
}
}