CVE-2026-58201

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Lokka is a Model Context Protocol server for Microsoft 365, including Microsoft Graph and other services. Prior to 2.1.2, the Lokka-Microsoft tool in src/mcp/src/main.ts uses direct URL string concatenation to append the user-controlled path value to the management.azure.com base URL. A specially crafted path can alter URL authority parsing and cause an Azure Resource Manager bearer token to be sent to an unintended host. This issue is fixed in version 2.1.2.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
54(Track)
EG Risk 54/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 15, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
Patch available. Sources: github, github_pr, github_commit.
github_commit

commit babead878f44 (merill/lokka)

Fix landed in merill/lokka commit babead878f44 — awaiting tagged release

https://github.com/merill/lokka/commit/babead878f44cc2face2f8ee55d8b706e420947e
github_pr

Security: Fix SSRF/token exfiltration vulnerability using URL standar…

Fix merged in merill/lokka PR #47 on 2026-06-19 — awaiting tagged release

https://github.com/merill/lokka/pull/47
github Patch Available

Azure Resource Manager URL path validation issue in Lokka · Advisory · merill/lokka · GitHub

https://github.com/merill/lokka/security/advisories/GHSA-g2gw-q38m-vjfc

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 23:45 UTCEG score recompute
  2. 2026-09-20 20:16 UTCEPSS rescore
  3. 2026-09-19 23:05 UTCEG score recompute
  4. 2026-09-18 22:27 UTCEG score recompute
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-17 21:50 UTCEG score recompute
  7. 2026-09-17 19:31 UTCEPSS rescore
  8. 2026-09-16 21:12 UTCEG score recompute
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-15 19:38 UTCEG score recompute
  11. 2026-09-15 19:13 UTCEG score recompute
  12. 2026-09-15 17:32 UTCEG score recompute
  13. 2026-09-15 16:53 UTCEG score recompute
  14. 2026-09-15 16:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58201?
CVE-2026-58201 is a high vulnerability published on September 15, 2026. Lokka is a Model Context Protocol server for Microsoft 365, including Microsoft Graph and other services. Prior to 2.1.2, the Lokka-Microsoft tool in src/mcp/src/main.ts uses direct URL string concatenation to append the user-controlled path value to the management.azure.com base URL. A specially…
When was CVE-2026-58201 disclosed?
CVE-2026-58201 was first published in the National Vulnerability Database on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58201 actively exploited?
CVE-2026-58201 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.7% of all scored CVEs.
What is the CVSS score of CVE-2026-58201?
CVE-2026-58201 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-58201?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58201, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58201

Explore →

Is Your Infrastructure Affected by CVE-2026-58201?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs