# CVE-2026-81030: Mage AI through 0.9.79 Arbitrary File Read via Unvalidated Path in browser_items Endpoint

> Attackers with Viewer role can read arbitrary files on the server via unvalidated path in browser_items endpoint, bypassing project directory restrictions.

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-7m4p-j4m3-pqmc, MINI-jh7f-vrq3-phfh

## What is CVE-2026-81030?

CVE-2026-81030 is a high-severity path traversal vulnerability in mage-ai, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-81030?


## How do I fix CVE-2026-81030?

Apply the vendor's patch.

## Is CVE-2026-81030 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81030 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81030 and fix it if it is affected.

What it is: CVE-2026-81030 is a high-severity path traversal vulnerability in mage-ai, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81030 exists.

Affected product: mage-ai. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-81030/ (Markdown: https://insights.sbomify.com/CVE-2026-81030/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81030
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81030
- OSV: https://osv.dev/vulnerability/CVE-2026-81030

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-81030/
Summaries are generated and may contain mistakes; the official description above is the record.