Skip to content

AAK-MCP-METAMCP-CVE-2026-79538-001: MetaMCP image up to 2.4.22: inspector proxy code execution and cross-tenant session dispatch (no fixed release)

Severity
CRITICAL
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/container_image_pins.py
Auto-fixable
No.
SARIF name
MetaMcpImageInspectorProxyRce

What it detects

MetaMCP, a self-hosted MCP aggregator and gateway, ships as the container image ghcr.io/metatool-ai/metamcp, which its compose file pulls at :latest. Its root package.json is private, and npm's @metamcp/mcp-server-metamcp is a separate client proxy, so the image tag is the only thing that carries its version. Up to and including 2.4.22 the internal MCP inspector proxy endpoint GET /mcp-proxy/server/stdio takes the STDIO process parameters from the request instead of from a server record the caller owns, so any logged-in user (self-registration is on by default) can run commands in the application container (CVE-2026-79538, CVSS 3.1 9.8, CWE-94). Through 2.4.22 the session store is keyed only by the client-supplied mcp-session-id, the endpoint middleware never checks who owns the session, and GET /metamcp/health/sessions lists live session IDs without authentication, so a caller can list and call another tenant's MCP tools with that tenant's forwarded credentials (CVE-2026-79537, CVSS 9.1, CWE-639). There is no fixed release: 2.4.22 (2025-12-19) is the newest release and image tag, and the TraceForce advisories NVD cites list 2.4.22 and the newest main commit as affected with no patched version. On 2026-10-03 the latest, 2 and 2.4 tags were the same image as 2.4.22, so latest and an untagged reference are reported too.

How to fix

There is no patched image to move to. Keep MetaMCP off public networks, block the /mcp-proxy/ and /metamcp/health/ paths at the reverse proxy, turn off open self-registration, and rotate every secret in the environment of a deployment that was exposed.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-METAMCP-CVE-2026-79538-001

Limitations

Reads image references only: an image: value or any other mention of REPO:TAG in YAML (compose files, Kubernetes manifests, MCP configs), a Helm values mapping of repository (or registry + repository) and tag, Dockerfile and Containerfile FROM, and docker run arguments in *mcp*.json and claude_desktop_config.json. A tag that is not a version (main, main-20250617, dev), a digest with no tag, an interpolated tag (:${VERSION}, {{ .Values.tag }}) and a Helm tag left empty (the chart's appVersion decides) state no version and are not reported. A two-part tag such as 0.24 stands for the newest patch on that line and is reported only when the whole line sits below the fixed version. Mirrors under another registry are not matched, and commented-out lines are skipped. latest and an untagged reference are reported because latest was 2.4.22 on 2026-10-03; once a fixed image takes latest, that arm reports a patched deployment until the pin moves. The floating 2 and 2.4 tags are not reported, though both were 2.4.22 on that date. A release after 2.4.22 is outside NVD's range and is not reported, which is not a claim that it is fixed.

References

  • CVE: CVE-2026-79538, CVE-2026-79537
  • OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering), MCP05:2025 (Command Injection & Execution), MCP10:2025 (Context Injection & Over-Sharing)
  • OWASP Agentic Top 10: ASI04 (Agentic Supply Chain Vulnerabilities), ASI05 (Unexpected Code Execution (RCE))
  • Adversa AI MCP Top 25 (AAK-defined ids): ADV-INJECT-01 (Shell Injection via MCP), ADV-AUTH-01 (Missing Authentication)
  • CSA AI Controls Matrix (AICM): IAM-01, IVS-04, STA-08

All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-METAMCP-CVE-2026-79538-001.md: the page then shows that text, with the registry reference appended under it.