Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Local-only vector with low privileges required; impact is read-only limited confidentiality with no integrity or availability consequence per the description.
Primary rating from Vendor (vuldb).
CVSS VectorVendor: vuldb
Lifecycle Timeline
1DescriptionCVE.org
A vulnerability was determined in FoundationAgents MetaGPT up to 0.8.2. This affects the function read of the file metagpt/tools/libs/editor.py. This manipulation causes path traversal. The attack needs to be launched locally. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
AnalysisAI
Path traversal in MetaGPT versions 0.8.0 through 0.8.2 (FoundationAgents) allows a local low-privileged attacker to read arbitrary files on the host system via the read function in metagpt/tools/libs/editor.py. Impact is limited to confidentiality - no write or availability impact is present. A public proof-of-concept exploit has been disclosed on GitHub; no vendor patch exists as the vendor did not respond to coordinated disclosure.
Technical ContextAI
MetaGPT is an LLM-based multi-agent framework where AI agents collaborate on software engineering tasks. The affected component is the read function in metagpt/tools/libs/editor.py, a tool that agents use to read filesystem content during task execution. CWE-22 (Path Traversal) identifies the root cause: the function accepts file path input without adequately sanitizing directory traversal sequences (e.g., ../), allowing input to escape the intended working directory scope and reference arbitrary files on the local filesystem. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N/VC:L) confirms local-only reach, low privilege requirement, no special attack conditions, and limited confidentiality impact. No CPE strings were provided, but affected versions are explicitly identified as MetaGPT 0.8.0, 0.8.1, and 0.8.2 per EUVD-2026-54294.
RemediationAI
No vendor-released patch has been identified at time of analysis - the vendor did not respond to coordinated disclosure despite early contact. As a primary compensating control, deploy MetaGPT inside a container or chroot jail with filesystem access restricted strictly to required working directories, preventing traversal from reaching sensitive paths even if the vulnerability is triggered. Operators can also apply a local code patch normalizing file paths (e.g., using Python's os.path.realpath or pathlib.Path.resolve with a prefix check) before they are passed to the read function; this resolves the root cause but requires maintaining a fork. OS-level mandatory access controls (AppArmor profiles, SELinux policies, or seccomp filters) can restrict which files the MetaGPT process is permitted to open. Monitor application logs for traversal sequences (../) in file path arguments as a detection measure. Until an official patch is available, restrict local system access to MetaGPT deployments to trusted users only. Reference: VulDB advisory at https://vuldb.com/vuln/386516.
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-54294
GHSA-x7c6-rrf2-hrj9