Is @azure/msal-node 6.0 vulnerable?
npm · 2 releases from 6.0.0 to 6.0.1 · latest @azure/msal-node is 7.2.2 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. @azure/msal-node 6.0.1, the last 6.0 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.
npm install @azure/msal-node@7.1.0Is your project on an affected @azure/msal-node?
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 6.0.1
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 6.0.x release
Affected: 6.0.0 to 6.0.1. Latest @azure/msal-node: 7.2.2.
| Version | Known advisories |
|---|---|
| @azure/msal-node 6.0.1 | CVE-2026-109461 |
| @azure/msal-node 6.0.0 | CVE-2026-109461 |
Which of your client projects are still on @azure/msal-node 6.0?
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.