p PatchFirst

CVE-2026-46417

CVE-2026-46417 · Angular: SSRF via Hostname Hijacking in @angular/platform-server

This page contains facts from public vulnerability sources. Check the original advisory before updating.

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-next.12, 21.2.13, 20.3.21, and 19.2.22, 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. This vulnerability is fixed in 22.0.0-next.12, 21.2.13, 20.3.21, and 19.2.22.

CVSS 8.8 · High · EPSS 0.4% · Fix available

Published
Updated

Stack: system · node

Affected products and versions

  • angular

    Versions
    • >= 22.0.0-next.0, < 22.0.0-next.12: Affected
    • >= 21.0.0-next.0, < 21.2.13: Affected
    • >= 20.0.0-next.0, < 20.3.21: Affected
    • >= 19.0.0-next.0, < 19.2.22: Affected
    • <= 18.2.14: Affected

    No fix published

  • angular.js Debian:12

    Versions
    • 1.8.3-1
    • 1.8.3-1+deb12u1
    • 1.8.3-1+deb12u1~deb11u1
    • 1.8.3-2
    • 1.8.3-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Debian:13

    Versions
    • 1.8.3-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • @angular/platform-server npm

    Affected ranges
    • SEMVER: ≥ 22.0.0-next.0, < 22.0.0-next.12

    Update to 22.0.0-next.12

  • @angular/platform-server npm

    Affected ranges
    • SEMVER: ≥ 21.0.0-next.0, < 21.2.13

    Update to 21.2.13

  • @angular/platform-server npm

    Affected ranges
    • SEMVER: ≥ 20.0.0-next.0, < 20.3.21

    Update to 20.3.21

  • @angular/platform-server npm

    Affected ranges
    • SEMVER: ≥ 19.0.0-next.0, < 19.2.22

    Update to 19.2.22

  • @angular/platform-server npm

    Affected ranges
    • SEMVER: ≤ 18.2.14

    No fix published

  • angular.js Ubuntu:Pro:16.04:LTS

    Versions
    • 1.2.28-1ubuntu2
    • 1.2.28-1ubuntu2+esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Ubuntu:Pro:18.04:LTS

    Versions
    • 1.5.10-1
    • 1.5.10-1ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Ubuntu:Pro:20.04:LTS

    Versions
    • 1.5.10-1
    • 1.7.9-1
    • 1.7.9-1ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Ubuntu:22.04:LTS

    Versions
    • 1.8.2-2
    • 1.8.2-2ubuntu0.1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Ubuntu:24.04:LTS

    Versions
    • 1.8.3-1
    • 1.8.3-1ubuntu0.24.04.1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Ubuntu:25.10

    Versions
    • 1.8.3-1
    • 1.8.3-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Ubuntu:26.10

    Versions
    • 1.8.3-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • angular.js Ubuntu:26.04:LTS

    Versions
    • 1.8.3-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →