ACVE-2026-0009

The configuration

Configuration label

@azure/mcp

Affected entries

• npm: @azure/mcp — SEMVER (introduced 0; fixed 1.0.0)
• MCP: pkg:npm/@azure/mcp — SEMVER (introduced 0; fixed 1.0.0)

Matcher

• some mcpServers
  • package eq "pkg:npm/@azure/mcp"

Why it is exploitable

What the vulnerability is

This record is a provisional package-specific advisory for an Azure MCP Server claim. The affected component is represented as the npm package @azure/mcp, with a tentative fixed release of 1.0.0; the current references do not establish the package identity and release boundary well enough to state the underlying vulnerability mechanism as settled.

Which configuration is exposed

The matcher exposes any MCP server entry whose package is pkg:npm/@azure/mcp. It does not require a harness, transport, URL, server name, or resolved version. That means the combination making the rule match is simply a configured server with this package identity; the matcher cannot distinguish a vulnerable release from a fixed one.

How ACVE detects it

ACVE reads mcpServers[].package and compares it with the tentative PURL. It does not read mcpServers[].resolvedVersion, verify the registry that supplied the package, or inspect the server's tools. A package launched through npx may also have an unknown resolved version, so the finding is reported as possible until the package and release are grounded.

Fix

1. Run grounding to confirm the Azure package name, PURL, affected range, and fixed release.
2. After confirmation, upgrade the matching MCP package to the documented fixed release and refresh the lockfile.
3. Until then, remove or disable the server if it is not required.

Grounding needed

acve advisory ground must confirm the package name and PURL, the fixed release, and that CVE-2026-32211 aliases this Azure MCP Server issue. The current 1.0.0 boundary is (unverified — see Grounding needed).

References

See references for primary sources.

Underlying CVEs / aliases

• CVE-2026-32211

Detect

npx @pickbitsai/acve audit

For CI, emit SARIF with npx @pickbitsai/acve audit --format sarif --out acve.sarif --apply and upload it with GitHub code scanning.

Fix

Ground the Azure MCP package identity, then upgrade to its confirmed fixed release.

Validation

No validation entries recorded.

Grounding

• OSV: not found; checked-at 2026-09-20T02:43:29Z
• NVD: not found; checked-at 2026-09-20T02:43:29Z
• KEV: not listed in KEV; checked-at 2026-09-20T02:43:29Z

References

ADVISORY

• https://nvd.nist.gov/vuln/detail/CVE-2026-32211

REPORT

• https://azure.microsoft.com/en-us/updates/

FIX

• https://github.com/pickbitsai/acve/issues?q=CVE-2026-32211