CVE-2026-45227: Heym < 0.0.21 Sandbox Escape via Python Introspection
Heym before 0.0.21 contains a sandbox escape vulnerability in the custom Python tool executor that allows authenticated workflow authors to bypass sandbox restrictions by using object-graph introspection primitives. Attackers can use Python introspection techniques to recover the unrestricted __import__ function, import blocked modules such as os and subprocess, and access inherited backend environment variables containing database credentials and encryption keys to execute arbitrary host commands as the backend service user.
Security readout for executives and security teams
Plain-English summary
Heym versions before 0.0.21 may let a logged-in workflow author break out of the intended Python sandbox. That could expose backend secrets and allow commands to run as the Heym service account. Treat this as high urgency where untrusted or semi-trusted users can author workflows.
Executive priority
Prioritize remediation for any shared, internet-accessible, or multi-user Heym deployment. The business risk is unauthorized access to secrets and backend command execution from a feature intended for controlled workflow automation.
Technical view
The issue is a sandbox escape in Heym’s custom Python tool executor. The CVE states authenticated workflow authors can use Python object-graph introspection to regain restricted import capability, load blocked modules, read inherited environment secrets, and execute host commands as the backend service user.
Likely exposure
Exposure is likely limited to deployments running Heym before 0.0.21 where authenticated users can create or edit workflows using the custom Python tool executor. Risk increases if backend environment variables contain database credentials, encryption keys, or other sensitive operational secrets.
Exploitation context
The bundle does not show KEV listing or confirmed active exploitation. The CVSS vector indicates network reachability, low attack complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.
Researcher notes
Evidence supports a high-impact authenticated sandbox escape, but the bundle does not provide independent exploit-in-the-wild confirmation. Keep analysis tied to Heym before 0.0.21, the custom Python executor, authenticated workflow-author access, and the vendor patch/release references.
Mitigation direction
Upgrade Heym to version 0.0.21 or later.
Confirm the PR #94 or patch commit changes are present in deployed builds.
Restrict workflow-author permissions to trusted users until patched.
Rotate exposed backend secrets if compromise is suspected.
Review vendor guidance before applying compensating controls.
Validation and detection
Inventory Heym deployments and identify versions below 0.0.21.
Check whether custom Python tool execution is enabled.
Review which users can author or edit workflows.
Audit backend environment variables exposed to the Heym service.
Inspect logs for unusual workflow activity by authenticated users.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-693: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.