Quick answers
- Is CVE-2026-109362 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109362 being exploited in the wild.
- How severe is CVE-2026-109362?
- Medium severity, with a CVSS score of 5.4, published 12 October 2026.
- Which products and versions are affected?
- Heym before v0.0.113.
- Is there a fix for CVE-2026-109362?
- Yes: fixed in v0.0.113. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109362 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-109362?
- 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: v0.0.113
Technical details
The vulnerability is a broken access control flaw where workflow execution tokens (scoped to workflow:execute) are validated only by checking the token's signature, JTI, and that the minting user exists—but the minting user's current access to the workflow is never re-checked at execution time. When a collaborator's share is removed via remove_workflow_share, only the share row is deleted; no token revocation occurs. Attackers can mint tokens with TTLs up to 10 years and repeatedly execute the workflow after removal, and the workflow owner cannot enumerate or revoke tokens created by others.
Affected products
- Heym Heym before v0.0.113
Timeline
- 2026-09-22: disclosed
- 2026-10-12: advisory