@angular/platform-server
Affected
- introduced
22.0.0-next.0, fixed22.0.0-next.12(semver)
Fixed versions
22.0.0-next.12
Fix
- Fixed version
22.0.0-next.12npm install @angular/[email protected]
Advisory
Also known as: CVE-2026-46417
@angular/platform-server: SSRF via Hostname Hijacking
Impact
A 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.
When 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.
Consequently, any relative HttpClient requests or PlatformLocation.hostname references are redirected to the attacker controlled server, potentially exposing internal APIs or metadata services.
Fix Information
The vulnerability is mitigated by introducing an Allowlist Mechanism directly into the core rendering APIs.
The 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.
Patches
Workarounds
Developers 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 torenderApplication or renderModule.
// Example manual normalization in Express
app.get('*', (req, res, next) => {
const trustedHost = 'localhost:4000';
// Ensure the request target matches expectations
if (req.headers.host !== trustedHost) {
return res.status(403).send('Forbidden');
}
next();
});High Basis: The source's own band: HIGH
22.0.0-next.0, fixed 22.0.0-next.12 (semver)22.0.0-next.12
22.0.0-next.12npm install @angular/[email protected]21.0.0-next.0, fixed 21.2.13 (semver)21.2.13
21.2.13npm install @angular/[email protected]20.0.0-next.0, fixed 20.3.21 (semver)20.3.21
20.3.21npm install @angular/[email protected]19.0.0-next.0, fixed 19.2.22 (semver)19.2.22
19.2.22npm install @angular/[email protected]0, last affected 18.2.14 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0