Quick answers
- Is CVE-2026-67540 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67540 being exploited in the wild.
- How severe is CVE-2026-67540?
- Medium severity, with a CVSS score of 6.5, published 11 November 2026.
- Which products and versions are affected?
- Heym before 0.0.70.
- Is there a fix for CVE-2026-67540?
- Yes: fixed in 0.0.70. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67540 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-67540?
- 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.70
Technical details
The get_workflow_template and get_node_template API endpoints lacked tenant visibility predicates, allowing any authenticated user to enumerate and read private (visibility=specific_users) templates owned by other tenants via horizontal IDOR. The list endpoints correctly enforced visibility, but the single-item fetch and use paths did not, enabling attackers to access template graphs, embedded email addresses, and configuration details without authorization. The fix centralizes visibility logic and gates GET and use handlers with visibility checks, returning 404 for inaccessible templates.
Affected products
- Heym Heym before 0.0.70
Timeline
- 2026-11-11: disclosed