dbcve.org
MetagptApplication · Deepwisdom

CVE-2026-5972

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to after 0.8.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in FoundationAgents MetaGPT up to 0.8.1. This issue affects the function Terminal.run_command in the library metagpt/tools/libs/terminal.py. The manipulation leads to os command injection. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. The identifier of the patch is d04ffc8dc67903e8b327f78ec121df5e190ffc7b. Applying a patch is the recommended action to fix this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability in the Terminal.run_command function in metagpt/tools/libs/terminal.py of MetaGPT up to version 0.8.1 allows remote attackers to execute arbitrary OS commands via manipulated input. The vulnerability is exploitable remotely and a public exploit exists.

MitigationApply patch d04ffc8dc67903e8b327f78ec121df5e190ffc7b to upgrade MetaGPT beyond version 0.8.1, or implement proper input validation and sanitization on all parameters passed to Terminal.run_command to prevent command injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MetagptApplication
Affected:<= 0.8.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed MetaGPT version
    Run: pip show metagpt or import metagpt; print(metagpt.__version__)
    Affected if Version is 0.8.1 or lower, or version cannot be determined (indicating older install)
  2. Locate vulnerable terminal.py file
    Find metagpt/tools/libs/terminal.py in your Python environment site-packages or project directory
    Affected if The file exists and contains the Terminal.run_command function
  3. Inspect run_command function for input handling
    Open metagpt/tools/libs/terminal.py and examine the run_command method for lack of input sanitization
    Affected if The function accepts user input and passes it directly to shell execution (e.g., os.system, subprocess with shell=True) without sanitization
  4. Determine if Terminal class is exposed to user input
    Review how Terminal.run_command is called - check if web interfaces, APIs, or other input sources can invoke it
    Affected if The Terminal.run_command function is accessible via external input (HTTP API, user-provided scripts, or agent inputs)

You are affected if you have MetaGPT version 0.8.1 or lower AND the Terminal.run_command function is accessible with unsanitized user input reaching shell execution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.8.1
Vendor patch github.com →
Interim mitigation

Apply patch d04ffc8dc67903e8b327f78ec121df5e190ffc7b to upgrade MetaGPT beyond version 0.8.1, or implement proper input validation and sanitization on all parameters passed to Terminal.run_command to prevent command injection.

Recommended fix Moderate confidence
  1. Review the vulnerable code in metagpt/tools/libs/terminal.py, specifically the Terminal.run_command function to identify the command injection point
  2. Apply the patch from commit d04ffc8dc67903e8b327f78ec121df5e190ffc7b to your local installation
  3. Verify the patch was applied correctly by reviewing the changes to the terminal.py file
  4. Test the fixed implementation to ensure the command injection vulnerability is resolved and legitimate functionality still works
  5. If using MetaGPT in production, consider upgrading to a newer version once available that incorporates this security fix

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Metagpt Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5972 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5972 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data