Description
A path traversal vulnerability in the SPO extension of MetaGPT 0.8.1 allows an attacker to read arbitrary files via the FILE_NAME value used by set_file_name() and load_meta_data() in metagpt/ext/spo/utils/load.py. The vulnerable code joins the attacker-controlled FILE_NAME value with the settings directory and opens the resulting path without validating that the resolved path remains within the intended directory.
Published: 2026-08-31
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A path traversal flaw in the SPO extension of MetaGPT 0.8.1 permits an attacker to read files outside the intended settings directory. The code constructs a file path by combining an attacker‑supplied FILE_NAME value with the server’s configuration directory and then opens the resulting file without verifying that the resolved path remains inside that directory. If exploited, the adversary can access any file that the process can read, including configuration files, credentials, or other sensitive data, leading to disclosure of confidential information and potential further compromise of the host system.

Affected Systems

The vulnerability exists in MetaGPT 0.8.1, specifically within the SPO extension, where the set_file_name() and load_meta_data() functions in metagpt/ext/spo/utils/load.py are affected. No additional vendor or product versions are identified.

Risk and Exploitability

Because the code accepts a user‑controlled file name, an attacker who can trigger the load_meta_data() routine—such as through an API request or user interface—can craft a path like "../../../../etc/passwd" to read arbitrary files. The exploit does not require elevated privileges beyond those of the service process. While no EPSS score is available and the vulnerability is not listed in the CISA KEV catalog, the potential to disclose sensitive data makes it a high‑risk issue. The severity of the flaw derives from the ability to read any file the process can access, a characteristic commonly categorized as a high‑severity issue.

Generated by OpenCVE AI on August 31, 2026 at 21:28 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to a fixed version of MetaGPT that eliminates the path concatenation flaw
  • Implement file‑path validation or sanitization before calling set_file_name() to ensure the resolved path remains within the intended directory
  • Restrict the execution environment of MetaGPT, limiting its file system access to only the directories required for operation

Generated by OpenCVE AI on August 31, 2026 at 21:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 31 Aug 2026 21:45:00 +0000

Type Values Removed Values Added
Title Path Traversal in MetaGPT SPO Extension Exposes Arbitrary Files
Weaknesses CWE-22

Mon, 31 Aug 2026 20:45:00 +0000

Type Values Removed Values Added
Description A path traversal vulnerability in the SPO extension of MetaGPT 0.8.1 allows an attacker to read arbitrary files via the FILE_NAME value used by set_file_name() and load_meta_data() in metagpt/ext/spo/utils/load.py. The vulnerable code joins the attacker-controlled FILE_NAME value with the settings directory and opens the resulting path without validating that the resolved path remains within the intended directory.
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2026-08-31T20:34:39.904Z

Reserved: 2026-08-25T00:00:00.000Z

Link: CVE-2026-79407

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-31T21:17:48.900

Modified: 2026-08-31T21:17:48.900

Link: CVE-2026-79407

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-31T21:30:05Z

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')