Is @azure/identity 1.2 vulnerable?

npm · 6 releases from 1.2.0 to 1.2.5 · latest @azure/identity is 4.14.1 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. @azure/identity 1.2.5, the last 1.2 release, is affected by 1 known security advisory (1 medium), including CVE-2024-35255. Upgrade to 4.2.1 or later to fix all of them.

Upgrade with:npm install @azure/identity@4.2.1

Is your project on an affected @azure/identity?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several JavaScript apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting @azure/identity 1.2.5

  • MediumCVE-2024-35255GHSA-m5vv-6r4h-3vj911 Jun 2024

    Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability

    Affected
    <4.2.1
    Fixed in
    4.2.1

Every @azure/identity 1.2.x release

Affected: 1.2.0 to 1.2.5. Latest @azure/identity: 4.14.1.

VersionKnown advisories
@azure/identity 1.2.5CVE-2024-35255
@azure/identity 1.2.4CVE-2024-35255
@azure/identity 1.2.3CVE-2024-35255
@azure/identity 1.2.2CVE-2024-35255
@azure/identity 1.2.1CVE-2024-35255
@azure/identity 1.2.0CVE-2024-35255

Which of your client projects are still on @azure/identity 1.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact @azure/identity version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other @azure/identity versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.