Vulnerability in FoundationAgents MetaGPT (CVE-2026-11455)
Summary
Vulnerability in FoundationAgents MetaGPT (CVE-2026-11455). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A vulnerability was determined in FoundationAgents MetaGPT up to 0.8.2. Affected by this issue is the function check_cmd_exists of the file metagpt/utils/common.py. This manipulation of the argument mermaid.path causes command injection. The attack may be initiated remotely. A high degree of complexity is needed for the attack. The exploitation is known to be difficult. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-11455 has been found in FoundationAgents MetaGPT.
Risk of unauthorized operations or information disclosure. CVSS score: 5.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "FoundationAgents MetaGPT CVE-2026-11455" on the vendor's site.
CVE-2026-11455 (FoundationAgents MetaGPT) — CWE-74 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-74) exists in FoundationAgents MetaGPT.
Check the vendor advisory for the affected versions of FoundationAgents MetaGPT.
Severity: Medium (CVSS 5.0/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで FoundationAgents MetaGPT を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory vuldb.com
- advisory vuldb.com
- advisory vuldb.com
- advisory nvd.nist.gov
- advisory github.com
- report github.com
- report vuldb.com
- report notion.so
- web github.com
- web github.com
- web github.com