CVE-2026-26118: Azure MCP Server Tools Elevation of Privilege Vulnerability
Noroxi assessment
Priority: Monitor (action score 35/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 65.1% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Azure MCP Server Tools 1.0.0 (npm) 1.0.2; Azure MCP Server Tools 1.0.0 (NuGet) 1.0.2; Azure MCP Server Tools 2.0.0 (npm) 2.0.0-beta.17.
Low priority for now. Upgrade to Azure MCP Server Tools 1.0.0 (npm) 1.0.2; Azure MCP Server Tools 1.0.0 (NuGet) 1.0.2; Azure MCP Server Tools 2.0.0 (npm) 2.0.0-beta.17 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Server-side request forgery (ssrf) in Azure MCP Server allows an authorized attacker to elevate privileges over a network.
- Published
- Mar 10, 2026
- Updated
- Jun 19, 2026
- EPSS
- 1.0% · 65th percentile
- CWE
- CWE-918
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | azure mcp server | cpe:2.3:a:microsoft:azure_mcp_server |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Azure MCP Server Tools 1.0.0 (npm)
- 1.0.0 and later · before 1.0.2affected
Microsoft Azure MCP Server Tools 1.0.0 (NuGet)
- 1.0.0 and later · before 1.0.2affected
Microsoft Azure MCP Server Tools 2.0.0 (npm)
- 2.0.0-beta.1 and later · before 2.0.0-beta.17affected
Microsoft Azure MCP Server Tools 2.0.0 (NuGet)
- 2.0.0-beta.1 and later · before 2.0.0-beta.17affected
Microsoft Azure MCP Server Tools 2.0.0 (PyPi)
- 2.0.0-beta.1 and later · before 2.0.0-beta.17affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft azure mcp serverbefore 2.0.0
- microsoft azure mcp server2.0.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | @azure/mcp | from 1.0.0 · before 1.0.2 | 1.0.2 |
| npm | @azure/mcp | from 2.0.0-beta.1 · before 2.0.0-beta.17 | 2.0.0-beta.17 |
| NuGet | Azure.Mcp | from 1.0.0 · before 1.0.2 | 1.0.2 |
| NuGet | Azure.Mcp | from 2.0.0-beta.1 · before 2.0.0-beta.17 | 2.0.0-beta.17 |
| PyPI | msmcp-azure | from 2.0.0b14 · before 2.0.0b17 | 2.0.0b17 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Azure MCP Server Tools 1.0.0 (npm) | 1.0.2 · Release Notes | Microsoft (MSRC) |
| Azure MCP Server Tools 1.0.0 (NuGet) | 1.0.2 · Release Notes | Microsoft (MSRC) |
| Azure MCP Server Tools 2.0.0 (npm) | 2.0.0-beta.17 · Release Notes | Microsoft (MSRC) |
| Azure MCP Server Tools 2.0.0 (NuGet) | 2.0.0-beta.17 · Release Notes | Microsoft (MSRC) |
| Azure MCP Server Tools 2.0.0 (PyPi) | 2.0.0-beta.17 · Release Notes | Microsoft (MSRC) |
| npm:@azure/mcp | 1.0.2 | Package registry (OSV) |
| npm:@azure/mcp | 2.0.0-beta.17 | Package registry (OSV) |
| NuGet:Azure.Mcp | 1.0.2 | Package registry (OSV) |
| NuGet:Azure.Mcp | 2.0.0-beta.17 | Package registry (OSV) |
| PyPI:msmcp-azure | 2.0.0b17 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:2 | 2026-03-17 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+6 d
- TodayNov 16, 2026+251 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.