Is @azure/msal-node 5.1 vulnerable?

npm · 6 releases from 5.1.0 to 5.1.5 · latest @azure/msal-node is 7.2.2 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. @azure/msal-node 5.1.5, the last 5.1 release, is affected by 1 known security advisory (1 high), including CVE-2026-109461. Upgrade to 7.1.0 or later to fix all of them.

Upgrade with:npm install @azure/msal-node@7.1.0

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

Advisories affecting @azure/msal-node 5.1.5

  • HighCVE-2026-109461GHSA-xcx6-jx8p-x3h523 Oct 2026

    MSAL Node authorization code flow may disclose parameters to an attacker-controlled endpoint

    Affected
    >=5.0.0-beta.0 <7.1.0
    Fixed in
    7.1.0

Every @azure/msal-node 5.1.x release

Affected: 5.1.0 to 5.1.5. Latest @azure/msal-node: 7.2.2.

VersionKnown advisories
@azure/msal-node 5.1.5CVE-2026-109461
@azure/msal-node 5.1.4CVE-2026-109461
@azure/msal-node 5.1.3CVE-2026-109461
@azure/msal-node 5.1.2CVE-2026-109461
@azure/msal-node 5.1.1CVE-2026-109461
@azure/msal-node 5.1.0CVE-2026-109461

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

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.