# CVE-2026-58201: Lokka: Azure Resource Manager URL path validation issue

> An attacker can manipulate URL paths to leak Azure Resource Manager bearer tokens to unintended hosts in the Lokka MCP server.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-g2gw-q38m-vjfc

## What is CVE-2026-58201?

CVE-2026-58201 is a high-severity server-side request forgery vulnerability in merill lokka, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-58201?

2 open source packages ship an affected version, including @merill/lokka.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@merill/lokka` | npm | All versions | 2.1.2 |
| `@merill/lokka` | npm | All versions | 2.1.2 |

## How do I fix CVE-2026-58201?

Upgrade @merill/lokka to 2.1.2 or later.

## Is CVE-2026-58201 being exploited?

There is no known exploitation of CVE-2026-58201 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-58201 and fix it if it is affected.

What it is: CVE-2026-58201 is a high-severity server-side request forgery vulnerability in merill lokka, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-58201 in the wild and no public exploit code.

Affected packages and fixed versions:
- @merill/lokka (npm): affected all versions; fixed in 2.1.2
- @merill/lokka (npm): affected all versions; fixed in 2.1.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-58201/ (Markdown: https://insights.sbomify.com/CVE-2026-58201/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-58201
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-58201
- OSV: https://osv.dev/vulnerability/CVE-2026-58201

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-58201/
Summaries are generated and may contain mistakes; the official description above is the record.