heymrun Heym up to 0.0.70 Workflow Engine subprocess.Popen playwrightCode os command injection

Summaryinfo

A vulnerability identified as very critical has been detected in heymrun Heym up to 0.0.70. Impacted is the function subprocess.Popen of the component Workflow Engine. The manipulation of the argument playwrightCode leads to os command injection. This vulnerability is uniquely identified as CVE-2026-67544. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in heymrun Heym up to 0.0.70. It has been rated as very critical. This issue affects the function subprocess.Popen of the component Workflow Engine. The manipulation of the argument playwrightCode with an unknown input leads to a os command injection vulnerability. Using CWE to declare the problem leads to CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command before it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Heym builds and runs agentic systems and business-process automations on self-hosted infrastructure. Prior to version 0.0.71, Heym's workflow engine accepts an arbitrary Python code string in the playwrightCode field of a Playwright node. This string is written to a temporary .py file and executed directly by the backend process via subprocess.Popen([sys.executable, script_path]) with no sandboxing, AST validation, or role gate. Any authenticated user — including a freshly registered account — can achieve full remote code execution (RCE) on the backend host, running as the service process user (observed as root in the default Docker deployment). This issue has been patched in version 0.0.71.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-67544 since 07/29/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/11/2026). The attack technique deployed by this issue is T1202 according to MITRE ATT&CK.

Upgrading to version 0.0.71 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• heymrun

Name

• Heym

Version

• 0.0.1
• 0.0.2
• 0.0.3
• 0.0.4
• 0.0.5
• 0.0.6
• 0.0.7
• 0.0.8
• 0.0.9
• 0.0.10
• 0.0.11
• 0.0.12
• 0.0.13
• 0.0.14
• 0.0.15
• 0.0.16
• 0.0.17
• 0.0.18
• 0.0.19
• 0.0.20
• 0.0.21
• 0.0.22
• 0.0.23
• 0.0.24
• 0.0.25
• 0.0.26
• 0.0.27
• 0.0.28
• 0.0.29
• 0.0.30
• 0.0.31
• 0.0.32
• 0.0.33
• 0.0.34
• 0.0.35
• 0.0.36
• 0.0.37
• 0.0.38
• 0.0.39
• 0.0.40
• 0.0.41
• 0.0.42
• 0.0.43
• 0.0.44
• 0.0.45
• 0.0.46
• 0.0.47
• 0.0.48
• 0.0.49
• 0.0.50
• 0.0.51
• 0.0.52
• 0.0.53
• 0.0.54
• 0.0.55
• 0.0.56
• 0.0.57
• 0.0.58
• 0.0.59
• 0.0.60
• 0.0.61
• 0.0.62
• 0.0.63
• 0.0.64
• 0.0.65
• 0.0.66
• 0.0.67
• 0.0.68
• 0.0.69
• 0.0.70

Website

• Product: https://github.com/heymrun/heym/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion