Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8amended

@angular/platform-server: SSRF via Hostname Hijacking

CVE-2026-46417GHSA-rfh7-fxqc-q52v

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @angular/platform-server

    Affected
    >= 22.0.0-next.0, < 22.0.0-next.12>= 21.0.0-next.0, < 21.2.13>= 20.0.0-next.0, < 20.3.21>= 19.0.0-next.0, < 19.2.22<= 18.2.14
    Fixed in
    22.0.0-next.12, 19.2.22, 20.3.21, 21.2.13

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.8 · 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 · score source
EPSS
  • CVE-2026-46417: 0.36% estimated exploitation activity in the next 30 days; percentile 29.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-rfh7-fxqc-q52v

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-rfh7-fxqc-q52v

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46417

Advisory: @angular/platform-server: SSRF via Hostname Hijacking
IDs: CVE-2026-46417, GHSA-rfh7-fxqc-q52v
Record: https://patchnext.com/advisories/cve-2026-46417 (revision 3, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: @angular/platform-server 22.0.0-next.12, 21.2.13, 20.3.21, 19.2.22. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @angular/platform-server: affected >= 22.0.0-next.0, < 22.0.0-next.12; >= 21.0.0-next.0, < 21.2.13; >= 20.0.0-next.0, < 20.3.21; >= 19.0.0-next.0, < 19.2.22; <= 18.2.14; fixed in 22.0.0-next.12, 19.2.22, 20.3.21, 21.2.13

## Suggested inspection (read-only)
- `npm ls @angular/platform-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @angular/platform-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-rfh7-fxqc-q52v (OSV record GHSA-rfh7-fxqc-q52v lists affected ranges: npm @angular/platform-server >=22.0.0-next.0 =21.0.0-next.0 =20.0.0-next.0 =19.0.0-next.0 =0 <=18.2.14)
- Verified: https://github.com/advisories/GHSA-rfh7-fxqc-q52v (GitHub-reviewed advisory GHSA-rfh7-fxqc-q52v lists affected ranges: npm @angular/platform-server >=22.0.0-next.0 =21.0.0-next.0 =20.0.0-next.0 =19.0.0-next.0 =0 <=18.2.14)

Commands are suggestions: review each one before running it.

Loading voting…