Quick answers
- Is CVE-2026-45227 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45227 being exploited in the wild.
- How severe is CVE-2026-45227?
- High severity, with a CVSS score of 8.8, published 12 May 2026.
- Which products and versions are affected?
- Heymrun Heym < 0.0.21.
- Is there a fix for CVE-2026-45227?
- A patch was published on 2026-05-10: Fix merged in PR #94 and released in v0.0.21 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45227 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45227?
- Check whether you run Heymrun Heym at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A sandbox escape exists in the `python_tool_executor.py` component of Heym due to insufficient filtering of Python introspection primitives. While the environment attempted to blacklist dangerous builtins like `exec` and `__import__`, an attacker can use object-graph introspection (e.g., accessing `__subclasses__` via the `object` class) to recover the original `__builtins__` dictionary. This allows the importation of restricted modules such as `os` and `subprocess`. Furthermore, because the tool runner inherited the backend's environment variables and working directory, an attacker can extract sensitive secrets or execute commands as the backend service user. The vulnerability is fixed in version 0.0.21 by implementing AST-based validation and scrubbing the subprocess environment.
Affected products
- heymrun Heym < 0.0.21
Timeline
- 2026-05-10: patched: Fix merged in PR #94 and released in v0.0.21
- 2026-05-12: advisory: NVD and VulnCheck advisory published