CVE-2026-81030
MediumCVSS 6.5Summary
Mage AI does not confine the paths accepted by its browser-items API to the project directory. A user with the Viewer role, which grants read access within the project, can read any file the server process can read by supplying an absolute path. Users with the Editor role can also write outside the project directory.
Risk Assessment
Privilege boundary violation can lead to leakage of sensitive system files, and for the Editor role, unauthorized file modification.
Recommendation
Update Mage AI to a version that includes a fix confining paths to the project directory, and enable the access control setting for this route.
Other vulnerabilities in Mage AI
Original NVD description (English source)
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.