Quick answers
- Is CVE-2026-67544 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67544 being exploited in the wild.
- How severe is CVE-2026-67544?
- High severity, with a CVSS score of 8.8, published 11 November 2026.
- Which products and versions are affected?
- Heym prior to 0.0.71.
- Is there a fix for CVE-2026-67544?
- Yes: fixed in 0.0.71. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67544 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-67544?
- Check whether you run 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.
How to fix
- Fixed in: 0.0.71
Technical details
The Playwright node in Heym's workflow engine accepts an arbitrary Python code string in the playwrightCode field, writes it to a temporary .py file, and executes it directly via subprocess.Popen with no sandboxing, AST validation, or access controls. Any authenticated user can exploit this to achieve remote code execution (RCE) as the backend service user. The fix in version 0.0.71 disables custom code by default and adds sandboxing when enabled.
Affected products
- Heym Heym prior to 0.0.71
Timeline
- 2026-11-11: disclosed
- 2026-07-18: patched: Version 0.0.71 released with fix