CVE-2026-81030

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-26. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
6.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists mage-ai versions up to and including 0.9.79 as affected. No release containing a fix is confirmed on record.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
The EG Score, 6.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 26, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Aug 26, 2026
No fix on record yet.
Web page

Mage AI through 0.9.79 Arbitrary File Read via Unvalidated Path in browser_items Endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/mage-ai-through-0.9.79-arbitrary-file-read-via-unvalidated-path-in-browser-items-endpoint
Web page

mage-ai/mage_ai/api/resources/BrowserItemResource.py at 0.9.79 · mage-ai/mage-ai · GitHub

https://github.com/mage-ai/mage-ai/blob/0.9.79/mage_ai/api/resources/BrowserItemResource.py
Web page

[Security] Arbitrary file read/write via /api/browser_items endpoint · Issue #6134 · mage-ai/mage-ai · GitHub

https://github.com/mage-ai/mage-ai/issues/6134
Web page

GitHub - mage-ai/mage-ai: 🧙 Build, run, and manage data pipelines for integrating and transforming data. · GitHub

https://github.com/mage-ai/mage-ai

Vendor Advisories for CVE-2026-81030(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 78× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 132 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 34 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-10-12 14:57 UTCEG score recompute
  4. 2026-10-11 19:21 UTCEG score recompute
  5. 2026-10-11 16:37 UTCEG score recompute
  6. 2026-10-11 13:55 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-10 06:06 UTCEG score recompute
  10. 2026-10-10 06:06 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-09 03:22 UTCEG score recompute
  13. 2026-10-09 03:22 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-08 01:50 UTCEG score recompute
  16. 2026-10-08 01:49 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-10-07 02:11 UTCEG score recompute
  19. 2026-10-07 02:11 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-10-06 02:46 UTCEG score recompute
  22. 2026-10-06 02:46 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  23. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-10-05 03:44 UTCEG score recompute
  25. 2026-10-05 03:44 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
Show 73 more
  1. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-04 04:24 UTCEG score recompute
  3. 2026-10-04 04:24 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  4. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-10-03 05:23 UTCEG score recompute
  6. 2026-10-03 05:23 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  7. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-02 06:21 UTCEG score recompute
  9. 2026-10-02 06:21 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  10. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-01 05:32 UTCEG score recompute
  12. 2026-10-01 05:32 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  13. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-09-30 06:03 UTCEG score recompute
  15. 2026-09-30 06:03 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  16. 2026-09-28 21:20 UTCEG score recompute
  17. 2026-09-28 21:20 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  18. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-09-27 19:37 UTCEG score recompute
  20. 2026-09-27 19:37 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  21. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-09-26 20:35 UTCEG score recompute
  23. 2026-09-26 20:35 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  25. 2026-09-24 21:14 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  26. 2026-09-24 14:43 UTCEG score recompute
  27. 2026-09-24 14:43 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  28. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  29. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  30. 2026-09-23 15:41 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  31. 2026-09-22 16:38 UTCEG score recompute
  32. 2026-09-22 16:38 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  33. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  34. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  35. 2026-09-21 17:21 UTCEG score recompute
  36. 2026-09-21 17:21 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  37. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  38. 2026-09-20 18:09 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  39. 2026-09-19 19:05 UTCEG score recompute
  40. 2026-09-19 19:04 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  41. 2026-09-18 20:00 UTCEG score recompute
  42. 2026-09-18 20:00 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  43. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  44. 2026-09-17 20:57 UTCEG score recompute
  45. 2026-09-17 20:57 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  46. 2026-09-16 21:47 UTCEG score recompute
  47. 2026-09-16 21:47 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  48. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  49. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  50. 2026-09-15 22:45 UTCEG score recompute
  51. 2026-09-15 22:44 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  52. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  53. 2026-09-14 23:40 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  54. 2026-09-13 23:55 UTCEG score recompute
  55. 2026-09-13 23:55 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  56. 2026-09-13 00:53 UTCEG score recompute
  57. 2026-09-13 00:53 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  58. 2026-09-12 01:51 UTCEG score recompute
  59. 2026-09-12 01:51 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  60. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  61. 2026-09-11 02:49 UTCEG score recompute
  62. 2026-09-11 02:49 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  63. 2026-09-10 03:47 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  64. 2026-09-09 04:44 UTCEG score recompute
  65. 2026-09-09 04:44 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  66. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  67. 2026-09-08 05:42 UTCEG score recompute
  68. 2026-09-08 05:41 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  69. 2026-09-07 06:37 UTCEG score recompute
  70. 2026-09-07 06:37 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5
  71. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  72. 2026-09-06 07:35 UTCEG score recompute
  73. 2026-09-06 07:35 UTCGHSA enrichmentGHSA-7m4p-j4m3-pqmc · GitHub severity HIGH · GitHub CVSS 6.5

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81030?
CVE-2026-81030 is a medium-severity vulnerability; its CVE record was published on August 26, 2026. 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…
When was CVE-2026-81030 made public?
CVE-2026-81030 was made public on August 26, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 26, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-81030 actively exploited?
CVE-2026-81030 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81030?
CVE-2026-81030 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-81030?
No fix for CVE-2026-81030 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists mage-ai versions up to and including 0.9.79 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-81030 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-81030

Explore →

Is Your Infrastructure Affected by CVE-2026-81030?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs