@angular/common vulnerabilities

Angular - commonly needed directives and services

Registry
npm
Latest
22.2.3
License
MIT

8 known advisories

The latest version, 22.2.3, is not affected by any of them. Projects on older versions may be.

Update to the latest version:npm install @angular/common@22.2.3

Security advisories for @angular/common

  • MediumGHSA-jfgx-762w-99vr20 Oct 2026

    @angular/common: XSRF Token Leakage via URL Parsing Discrepancy in Angular HTTP Client (Incomplete fix for CVE-2025-66035)

    Affected
    >=21.0.0 <21.0.3 · >=20.0.0 <20.3.34 · <=19.2.25
    Fixed in
    20.3.34, 21.0.3
  • MediumGHSA-p297-fm68-3q8c10 Sept 2026

    Angular: Information Leak via `HttpTransferCache` Bypass When Using `withRequestsMadeViaParent`

    Affected
    >=22.0.0 <22.1.1 · >=21.0.0 <21.2.20 · >=20.0.0 <20.3.28 · <=19.2.25
    Fixed in
    20.3.28, 21.2.20, 22.1.1
  • HighGHSA-jhpw-976m-542j3 Aug 2026

    Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning

    Affected
    >=22.0.0-next.0 <22.0.2 · >=21.0.0-next.0 <21.2.19 · >=20.0.0-next.0 <20.3.27 · <=19.2.25
    Fixed in
    20.3.27, 21.2.19, 22.0.2
  • HighGHSA-48r7-hpm6-gfxm15 Jun 2026

    @angular/common: Denial of Service (DoS) via OOM in Date Formatting (formatDate)

    Affected
    >=22.0.0-next.0 <22.0.1 · >=21.0.0-next.0 <21.2.17 · >=20.0.0-next.0 <20.3.25 · <=19.2.25
    Fixed in
    20.3.25, 21.2.17, 22.0.1
  • HighGHSA-39pv-4j6c-2g6v15 Jun 2026

    @angular/common: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning

    Affected
    >=22.0.0-next.0 <22.0.1 · >=21.0.0-next.0 <21.2.17 · >=20.0.0-next.0 <20.3.25 · <=19.2.25
    Fixed in
    20.3.25, 21.2.17, 22.0.1
  • HighGHSA-p3vc-36g9-x9gr15 Jun 2026

    @angular/common: Denial of Service (DoS) via OOM in Number Formatting (digitsInfo)

    Affected
    >=22.0.0-next.0 <22.0.0-rc.2 · >=20.0.0-next.0 <20.3.22 · >=19.0.0-next.0 <19.2.23 · <=18.2.14 · >=21.0.0-next.0 <21.2.15
    Fixed in
    19.2.23, 20.3.22, 21.2.15, 22.0.0-rc.2
  • HighGHSA-q6f4-qqrg-jv6x15 Jun 2026

    @angular/common: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache

    Affected
    >=22.0.0-next.0 <22.0.0-rc.2 · >=20.0.0-next.0 <20.3.22 · >=19.0.0-next.0 <19.2.23 · <=18.2.14 · >=21.0.0-next.0 <21.2.15
    Fixed in
    19.2.23, 20.3.22, 21.2.15, 22.0.0-rc.2
  • HighGHSA-58c5-g7wp-6w3726 Nov 2025

    Angular is Vulnerable to XSRF Token Leakage via Protocol-Relative URLs in Angular HTTP Client

    Affected
    >=21.0.0-next.0 <21.0.1 · >=20.0.0-next.0 <20.3.14 · <19.2.16
    Fixed in
    19.2.16, 20.3.14, 21.0.1

Which of your client projects still run an old @angular/common?

NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other npm packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.