ToolUniverse Python Package Vulnerability: Critical CVE-2026-81096
- Severity
- CRITICAL
- CVSS
- 10
- Affected component
- cve-2026-81096 (pypi)
- Affected versions
- >= v1.2.6, <= v1.2.6 or >= v1.2.5, <= v1.2.5 or >= v1.2.4, <= v1.2.4 or >= v1.2.3, <= v1.2.3 or >= v1.2.2, <= v1.2.2 or >= v1.2.1, <= v1.2.1 or >= v1.1.11, <= v1.1.11 or >= v1.1.10, <= v1.1.10 or >= v1.1.9, <= v1.1.9 or >= v1.1.8, <= v1.1.8 or >= v1.1.7, <= v1.1.7 or >= v1.1.4, <= v1.1.4 or >= v1.1.3, <= v1.1.3 or >= v1.1.2, <= v1.1.2 or >= v1.1.1, <= v1.1.1 or >= v1.0.22, <= v1.0.22 or >= v1.0.21, <= v1.0.21 or >= v1.0.19.1, <= v1.0.19.1 or >= v1.0.19, <= v1.0.19 or >= v1.0.18, <= v1.0.18 or >= v1.0.17.9, <= v1.0.17.9 or >= v1.0.17.8, <= v1.0.17.8 or >= v1.0.17.7, <= v1.0.17.7 or >= v1.0.17.6, <= v1.0.17.6 or >= v1.0.17.5, <= v1.0.17.5 or >= v1.0.17.4, <= v1.0.17.4 or >= v1.0.17.3, <= v1.0.17.3 or >= v1.0.17.2, <= v1.0.17.2 or >= v1.0.17.1, <= v1.0.17.1 or >= v1.0.17, <= v1.0.17 or >= v1.0.16, <= v1.0.16 or >= v1.0.15.7, <= v1.0.15.7 or >= v1.0.15.6, <= v1.0.15.6 or >= v1.0.15.5, <= v1.0.15.5 or >= v1.0.15.4, <= v1.0.15.4 or >= v1.0.15.3, <= v1.0.15.3 or >= v1.0.15.2, <= v1.0.15.2 or >= v1.0.15.1, <= v1.0.15.1 or >= mcpb, <= mcpb or >= v1.0.14.2, <= v1.0.14.2 or >= v1.0.14.1, <= v1.0.14.1 or >= v1.0.14, <= v1.0.14 or >= v1.0.13.2, <= v1.0.13.2 or >= v1.0.13.1, <= v1.0.13.1 or >= v1.0.12.7, <= v1.0.12.7 or >= v1.0.12.6, <= v1.0.12.6 or >= v1.0.12.5, <= v1.0.12.5 or >= v1.0.12.4, <= v1.0.12.4 or >= v1.0.12.3, <= v1.0.12.3 or >= v1.0.12.2, <= v1.0.12.2 or >= v1.0.12.1, <= v1.0.12.1 or >= v1.0.12, <= v1.0.12 or >= v1.0.11.2, <= v1.0.11.2 or >= v1.0.11.1, <= v1.0.11.1 or >= v1.0.11, <= v1.0.11 or >= v1.0.10, <= v1.0.10 or >= v1.0.9.1, <= v1.0.9.1 or >= v1.0.9, <= v1.0.9 or >= v1.0.8, <= v1.0.8
- Patched version
- 1.3.0
An early warning has been issued for a critical vulnerability in the ToolUniverse Python package. Versions before 1.3.0 are reportedly affected.
What happened
The ToolUniverse package is under investigation for a critical vulnerability. It appears to run caller-supplied Python code inside a sandbox that could be escaped, allowing unauthenticated remote code execution. Versions before 1.3.0 are affected. The vulnerability has been assigned CVE-2026-81096 with a CVSS score of 10.0. It is not yet confirmed to be exploited in the wild.
To assess your exposure, check if you are using any version of ToolUniverse before 1.3.0. The affected versions span a wide range, from v1.2.6 down to v1.0.8 and various patch versions in between. The primary sources should be consulted for the most accurate and up-to-date information.
What to do about it
- Upgrade to ToolUniverse version 1.3.0 or later to mitigate the risk of remote code execution.
- If you are unable to upgrade immediately, consider isolating the affected systems until the upgrade can be performed.
- Monitor the primary sources for updates on the vulnerability and any additional mitigation advice.
- Review your system logs for any signs of unauthorized activity that may indicate an attempted exploit of this vulnerability.
How 0Day would have caught this
cve-2026-81096 is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.
Frequently asked questions
Am I affected?
You are affected if you are using any version of ToolUniverse before 1.3.0. This includes all versions from v1.2.6 down to v1.0.8 and various patch versions in between.
What should I do right now?
Upgrade to ToolUniverse version 1.3.0 or later as soon as possible. If immediate upgrade is not feasible, isolate the affected systems and monitor for any signs of unauthorized activity.
Is there an official fix available?
Yes, the official fix is to upgrade to ToolUniverse version 1.3.0 or later.