CVE-2026-55376: heym Python Tool Sandbox Escape

Published Oct 13, 2026
·
Updated

Heym builds and runs agentic systems and business-process automations on self-hosted infrastructure. Prior to 0.0.40, an authenticated user who can create or edit a workflow with an Agent custom Python tool can bypass the blacklist-based sandbox in backend/app/services/pythontoolexecutor.py because allowed standard-library modules expose operating-system, process, and filesystem capabilities through public attributes that pass safeimport() and validatecodesafety(). The runner then executes the supplied tool with exec(), permitting commands and file operations as the backend application user; self-registration affects reachability, but portal triggering alone does not grant code control. This issue is fixed in 0.0.40.

Affected Software

1 affected component
Heym Heym<0.0.40

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.0.40

Event History

Oct 13, 2026
CVE Published
via MITRE·03:12 PM
Data Sourced
via MITRE·03:12 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated user must be able to create or edit a workflow containing an Agent custom Python tool. Merely being able to trigger workflows through the portal does not provide control over the Python code.

2

What access does successful exploitation provide?

The attacker can execute commands and perform file operations as the backend application user. The impact therefore depends on the permissions and accessible resources assigned to that backend user.

3

Are installations affected by default?

Exposure depends on whether users can create or edit workflows with Agent custom Python tools. Self-registration can affect whether an attacker can obtain an account, but it is not required if a user already has the necessary authenticated workflow-editing permissions.

4

What version fixes the issue?

The issue is fixed in Heym version 0.0.40. Versions prior to 0.0.40 are affected when the required workflow-editing capability is available.

5

What can be done if upgrading is not immediately possible?

Restrict creation and editing of workflows that use Agent custom Python tools to trusted administrators. Also limit the backend application user's operating-system, process, and filesystem permissions to reduce the impact of code execution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203