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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-109461: 0.36% estimated exploitation activity in the next 30 days; percentile 30.01 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Origin validation error in Microsoft Authentication Library (MSAL) for Node.js allows an unauthorized attacker to disclose information over a network. This affects the authcode flow. Patches Version 7.1.0 and higher are patched. Workarounds Ensure you pass in only the authcode to to acquireTokenByCode

Published by the source

23 Oct 2026, 22:16 UTC

Last modified by the source

23 Oct 2026, 22:30 UTC

Source last checked

26 Oct 2026, 13:07 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-xcx6-jx8p-x3h5

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-xcx6-jx8p-x3h5

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-xcx6-jx8p-x3h5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-109461

Advisory: MSAL Node authorization code flow may disclose parameters to an attacker-controlled endpoint
IDs: CVE-2026-109461, GHSA-xcx6-jx8p-x3h5
Record: https://patchnext.com/advisories/cve-2026-109461 (revision 3, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @azure/msal-node 7.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @azure/msal-node: affected >= 5.0.0-beta.0, < 7.1.0; fixed in 7.1.0

## Suggested inspection (read-only)
- `npm ls @azure/msal-node --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @azure/msal-node.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xcx6-jx8p-x3h5 (GitHub-reviewed advisory GHSA-xcx6-jx8p-x3h5 lists affected ranges: npm @azure/msal-node >=5.0.0-beta.0 <7.1.0)
- Verified: https://osv.dev/vulnerability/GHSA-xcx6-jx8p-x3h5 (OSV record GHSA-xcx6-jx8p-x3h5 lists affected ranges: npm @azure/msal-node >=5.0.0-beta.0 <7.1.0 (fixed))

Commands are suggestions: review each one before running it.