Skip to main content
VulnerabilityPublished Updated

CVE-2026-4516: Foundation Agents MetaGPT · Injection

Affects Foundation Agents MetaGPTSource CVE Database V5

0
Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 1 Nov 2026, 22:58 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Foundation AgentsMetaGPTAffected
  • =0.8.0
  • =0.8.1
Fixed in–
GitHubfoundation agents/MetaGPTpkg:github/foundation agents/MetaGPTOther threatsAffected
  • =0.8.0
  • =0.8.1
Fixed in–

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

AI-suggested

  1. Immediately restrict network access to MetaGPT instances, ensuring they are not exposed to untrusted or public networks.
  2. Implement strict input validation and sanitization on all inputs processed by the DataInterpreter component, particularly those handled by metagpt/actions/di/write_analysis_code.py, to prevent injection payloads.
  3. Monitor logs and network traffic for unusual or suspicious activity indicative of injection attempts or exploitation.
  4. Employ application-layer firewalls or runtime application self-protection (RASP) tools to detect and block injection attacks in real time.
  5. Isolate MetaGPT environments from critical production systems to limit potential impact.
  6. Engage with the vendor or community to track any forthcoming patches or updates and apply them promptly once available.
  7. Consider deploying compensating controls such as containerization or sandboxing of MetaGPT processes to limit the blast radius of a successful attack.
  8. Conduct regular security assessments and code reviews focusing on injection vulnerabilities within AI orchestration components.

Description

A vulnerability was found in Foundation Agents MetaGPT up to 0.8.1. This vulnerability affects unknown code of the file metagpt/actions/di/write_analysis_code.py of the component DataInterpreter. The manipulation results in injection. It is possible to launch the attack remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

References

Community reviews

Loading reviews…