Skip to main content
VulnerabilityPublished

CVE-2026-79538: metamcp · Code Injection

Affects metamcpSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubmetatool-ai/metamcppkg:github/metatool-ai/metamcpOther threatsAffected
  • <=2.4.22
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict access to the vulnerable endpoint and monitor for suspicious activity related to the MCP inspector proxy.

Description

metatool-ai MetaMCP versions up to and including 2.4.22 contain a critical remote code execution vulnerability in the internal MCP inspector proxy endpoint GET /mcp-proxy/server/stdio. This flaw allows unauthenticated attackers to execute arbitrary code on the affected system without user interaction.

References

Community reviews

Loading reviews…