Description
Mage AI does not confine the paths accepted by its browser-items API to the project directory. BrowserItemResource in mage_ai/api/resources/BrowserItemResource.py passes a caller-supplied path to the filesystem read and write helpers without calling the containment helper that the sibling FileContentResource and FileResource classes both use, so the resource contains no such call while those two contain several. A user holding the Viewer role, which grants read access within the project and nothing outside it, can therefore read any file the server process can read by supplying an absolute path. The permission model that would otherwise separate roles is not consulted for this route in the default configuration, because the setting that enables it defaults to false. Callers holding the Editor role additionally write through the same unconfined path, though that role is already able to execute code by design, so the boundary crossed by this flaw is the read available to the Viewer role.
Published: 2026-08-26
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized File Disclosure
Action: Patch
AI Analysis

Impact

Mage AI’s BrowserItemResource accepts a caller-supplied file path and forwards it to the filesystem read helper without enforcing containment checks. This omission allows a user with the Viewer role, which normally grants read access only within the project, to supply an absolute path and read any file that the server process can access, resulting in arbitrary file disclosure. The vulnerability corresponds to CWE‑22 (Path Traversal).

Affected Systems

The flaw affects Mage AI (the mage‑ai project) for versions up to and including 0.9.79. The issue arose in the BrowserItemResource within mage_ai/api/resources/BrowserItemResource.py and is present in the 0.9.79 release and any earlier releases that share the same codebase.

Risk and Exploitability

The CVSS score of 7.1 indicates a high severity. While EPSS data is not available, the vulnerability is not listed in the CISA KEV catalog. An attacker who can authenticate as a Viewer (or higher) and interact with the browser‑items API can supply absolute paths and read arbitrary files from the host. The exploit requires access to the application and the viewer role, implying that privileged users or compromised credentials can leverage this flaw. The lack of a containment check is the root cause, creating a clear high‑risk scenario for data leakage.

Generated by OpenCVE AI on August 26, 2026 at 18:38 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Mage AI to a version that implements path containment checks for the browser‑items endpoint.
  • If an update is not immediately available, modify the BrowserItemResource to reject absolute paths or enforce project‑bound path checks.
  • Limit the use of the browser‑items endpoint to administrators or roles with explicit approval, and review role assignments to ensure that Viewer users cannot access the vulnerable endpoint.

Generated by OpenCVE AI on August 26, 2026 at 18:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 26 Aug 2026 23:45:00 +0000

Type Values Removed Values Added
First Time appeared Mage Ai
Mage Ai mage Ai
Vendors & Products Mage Ai
Mage Ai mage Ai

Wed, 26 Aug 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Wed, 26 Aug 2026 16:00:00 +0000

Type Values Removed Values Added
Description Mage AI does not confine the paths accepted by its browser-items API to the project directory. BrowserItemResource in mage_ai/api/resources/BrowserItemResource.py passes a caller-supplied path to the filesystem read and write helpers without calling the containment helper that the sibling FileContentResource and FileResource classes both use, so the resource contains no such call while those two contain several. A user holding the Viewer role, which grants read access within the project and nothing outside it, can therefore read any file the server process can read by supplying an absolute path. The permission model that would otherwise separate roles is not consulted for this route in the default configuration, because the setting that enables it defaults to false. Callers holding the Editor role additionally write through the same unconfined path, though that role is already able to execute code by design, so the boundary crossed by this flaw is the read available to the Viewer role.
Title Mage AI through 0.9.79 Arbitrary File Read via Unvalidated Path in browser_items Endpoint
First Time appeared Mage
Mage mage-ai
Weaknesses CWE-22
CPEs cpe:2.3:a:mage:mage-ai:*:*:*:*:*:*:*:*
Vendors & Products Mage
Mage mage-ai
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Subscriptions

Mage Mage-ai
Mage Ai Mage Ai
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-26T16:05:12.110Z

Reserved: 2026-08-26T15:23:06.009Z

Link: CVE-2026-81030

cve-icon Vulnrichment

Updated: 2026-08-26T16:04:41.249Z

cve-icon NVD

Status : Received

Published: 2026-08-26T16:16:45.710

Modified: 2026-08-26T17:17:26.250

Link: CVE-2026-81030

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-26T23:30:12Z

Weaknesses
  • CWE-22

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