p PatchFirst

CVE-2026-50170

CVE-2026-50170 · Angular: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache

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-rc.2, 21.2.15, 20.3.22, and 19.2.23, a vulnerability was discovered in @angular/common when Server-Side Rendering (SSR) and hydration are enabled. The HttpTransferCache utility optimizes hydration by caching outgoing HTTP requests performed during SSR and transferring the cached state to the client-side application via TransferState. However, the caching mechanism fails to inspect the withCredentials flag or the Cookie header of outgoing requests. As a result, credentialed, user-specific responses may be cached by default in the shared TransferState payload. When these responses are serialized into the HTML, any caching layer (such as a CDN, reverse proxy, or shared server cache) that caches the SSR-rendered HTML page could inadvertently cache and leak one user's private data to other users, leading to a high-severity information disclosure vulnerability. This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23.

CVSS 8.2 · 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-rc.2: Affected
    • >= 21.0.0-next.0, < 21.2.15: Affected
    • >= 20.0.0-next.0, < 20.3.22: Affected
    • >= 19.0.0-next.0, < 19.2.23: 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/common npm

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

    Update to 22.0.0-rc.2

  • @angular/common npm

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

    Update to 20.3.22

  • @angular/common npm

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

    Update to 19.2.23

  • @angular/common npm

    Affected ranges
    • SEMVER: ≤ 18.2.14

    No fix published

  • @angular/common npm

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

    Update to 21.2.15

  • 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 →