Is @azure/msal-node 2.9 vulnerable?

npm · 3 releases from 2.9.0 to 2.9.2 · latest @azure/msal-node is 7.2.2 · checked 18 Nov 2026

No known advisories in the last release

@azure/msal-node 2.9.2, the last 2.9 release, has no known advisories. 1 advisory affects earlier 2.9.x releases, so update to 2.9.2.

Update within 2.9:npm install @azure/msal-node@2.9.2

Is your project on an affected @azure/msal-node?

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

Fixed within 2.9.x, affecting earlier releases

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

    Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability

    Affected
    >=2.7.0 <2.9.2
    Fixed in
    2.9.2

Every @azure/msal-node 2.9.x release

Affected: 2.9.0 to 2.9.1. 2.9.2 is not affected. Latest @azure/msal-node: 7.2.2.

VersionKnown advisories
@azure/msal-node 2.9.2None
@azure/msal-node 2.9.1CVE-2024-35255
@azure/msal-node 2.9.0CVE-2024-35255

Which of your client projects are still on @azure/msal-node 2.9?

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

Other @azure/msal-node 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.