CVE-2026-81096

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-27. A secondary CVSS source baseline 10.0; 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 week
10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

ToolUniverse ran caller-supplied Python inside a sandbox that could be escaped, on a server that required no authentication. The executor behind the python_code_executor tool, in python_executor_tool.py, inspected the submitted source for a denied list of attribute names and calls but left the attribute-lookup builtins available and did not stop a dunder attribute reached through a string lookup or through a module already permitted, so a caller could walk from a literal's class to its base and enumerate subclasses to obtain a reference to the process and subprocess modules. A per-call argument also let the caller widen the import allow-list before the inspection ran. The HTTP and MCP servers in http_api_server.py and smcp_server.py bound to every interface with debugging enabled and no authentication, so any caller able to reach the port executed code as the server process. Version 1.3.0 adds bearer-token authentication, defaults the bind address to loopback, and hardens the attribute checks.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
57th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 27, 2026

Last Modified

September 23, 2026

Advisory Details (3)

Auto-updated Oct 7, 2026
Patch available. Sources: github_pr.
Web page

ToolUniverse through 1.2.6 Unauthenticated Remote Code Execution via python_code_executor Sandbox Escape | Advisories | VulnCheck

https://www.vulncheck.com/advisories/tooluniverse-through-1.2.6-unauthenticated-remote-code-execution-via-python-code-executor-sandbox-escape
GitHub pull request Patch Available

Fix unauthenticated RCE in python_code_executor and harden server exposure

Patch available: mims-harvard/ToolUniverse v1.3.0 (PR #251 merged 2026-06-12)

https://github.com/mims-harvard/ToolUniverse/pull/251
Web page

GitHub - mims-harvard/ToolUniverse: Democratizing AI scientists with ToolUniverse · GitHub

https://github.com/mims-harvard/ToolUniverse

Vendor Advisories for CVE-2026-81096(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 28× in last 7d / 192× 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 100 of 332 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. None are among the latest 100 rows. The 232 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81096?
CVE-2026-81096 is a critical-severity vulnerability; its CVE record was published on August 27, 2026. ToolUniverse ran caller-supplied Python inside a sandbox that could be escaped, on a server that required no authentication. The executor behind the pythoncodeexecutor tool, in pythonexecutortool.py, inspected the submitted source for a denied list of attribute names and calls but left the…
When was CVE-2026-81096 made public?
CVE-2026-81096 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 27, 2026. EchelonGraph's copy of the record carries a last-modified date of September 23, 2026; the record at its source may have been updated since.
Is CVE-2026-81096 actively exploited?
CVE-2026-81096 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81096?
CVE-2026-81096 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-81096?
A fix for CVE-2026-81096 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-81096 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-81096?

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

Book a Demo →Browse All CVEs