CVE-2026-67544: high-severity vulnerability in heymrun heym
Heym: Playwright Custom Code Backend RCE via `playwrightCode` Field
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.8epss 1.0%
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected products
heymrun · heymRelated CVEs — heymrun heym
In the same product, most dangerous first.
CVE-2026-100864HIGHheym before 0.0.91 Remote Code Execution via Expression EngineEPSS 0.9%CVE-2026-130753HIGHheym before 0.0.142 Authenticated RCE via Playwright Step-Mode String FieldsEPSS 0.8%CVE-2026-67543HIGHHeym Unsandboxed skill code execution: skills run via a local backend subprocess without the Docker isolation that Python tools mandateEPSS 0.6%CVE-2026-67546HIGHHeym: Command execution via POST /api/mcp/fetch-tools stdio transport: supplied command is spawned before MCP validationEPSS 0.6%CVE-2026-67545HIGHHeym: Server-Side Request Forgery (SSRF) in HTTP Workflow NodeEPSS 0.5%CVE-2026-55376HIGHheym Python Tool Sandbox EscapeEPSS 0.5%