CVE-2026-81091

mcp-use inspector proxy could reach caller-selected internal targets

mcp-use · mcp-use · inspector proxy

First documented disclosure · Review checkpoint

Summary

A caller could make the inspector fetch internal services and read their replies.

Severity and exploitation evidence

High · 8.7/10 · CVSS 4.0. Severity source.

Exploitation not established: Reviewed public sources describe the weakness, a correction or a controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The proxy accepted destination headers/parameters without checking resolved hosts or redirect targets.

Conditions required

A caller can access the inspector proxy.

Potential impact

Internal network information disclosure.

Affected versions and configurations

CNA: mcp-use through 1.34.8.

Fix and mitigation status

The CNA describes guarded handling in the 2.x @mcp-use/inspector package, but no exact first fixed version is verified.

Practical next steps

Restrict the inspector to trusted users and egress destinations; verify the installed proxy’s resolved-address and redirect checks.

Operating lesson

Treat development proxy destinations as a server-side trust boundary.

Evidence and limits

Historical backfill. Referenced GitHub advisory returns 404. VulnCheck’s full original and CNA are available, but exact release-level remediation remains unresolved. CNA publication is 2026-08-27; this is distinct from the earliest reviewed public source and correction dates. VulnCheck assessments: CVSS 4.0 8.7; CVSS 3.1 8.6. Independent review correction: CNA datePublic is 2026-08-26; the original advisory was published 2026-08-27. Use the earlier authority-stated public date while retaining the date distinction.

Sources