{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81030 exists.","fix":"Apply the vendor's patch.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-81030 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81030 exists.\n\nAffected product: mage-ai. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-81030/ (Markdown: https://insights.sbomify.com/CVE-2026-81030/index.md)","id":"CVE-2026-81030","markdown":"https://insights.sbomify.com/CVE-2026-81030/index.md","name":"CVE-2026-81030","record":{"aliases":["GHSA-7m4p-j4m3-pqmc","MINI-jh7f-vrq3-phfh"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Mage AI data platform","requires_auth":"low_privilege","summary":"Attackers with Viewer role can read arbitrary files on the server via unvalidated path in browser_items endpoint, bypassing project directory restrictions.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Mage AI through 0.9.79 Arbitrary File Read via Unvalidated Path in browser_items Endpoint","id":"CVE-2026-81030","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"IDURAR ERP CRM through 4.1.1 Account Takeover via Unverified Identifier on Password Update","id":"CVE-2026-81031"},"packages":[],"prev":{"headline":"OpenMetadata before 2.0.0 JWT Disclosure via Unvalidated SAML and OIDC Redirect URI","id":"CVE-2026-81029"},"products":["mage-ai"],"published":"2026-08-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-26","vendors":["mage-ai"]},"summary":"Attackers with Viewer role can read arbitrary files on the server via unvalidated path in browser_items endpoint, bypassing project directory restrictions.","url":"https://insights.sbomify.com/CVE-2026-81030/"}