Quick answers
- Is CVE-2026-100862 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100862 being exploited in the wild.
- How severe is CVE-2026-100862?
- Medium severity, with a CVSS score of 4.9, published 27 September 2026.
- Which products and versions are affected?
- Heym prior to 0.0.91.
- Is there a fix for CVE-2026-100862?
- A patch was published on 2026-09-27: Fix released in version 0.0.91 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100862 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-100862?
- 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.
Technical details
Six distinct secret-handling gaps allow plaintext recovery: webhook auth headers are returned in API responses and persisted unsanitized to execution history; MCP API keys are stored and returned in plaintext, accepted via query strings (leaking to logs and proxies); portal session tokens are stored and validated by plaintext equality; workflow execution JWTs are stored in full and re-listed; Discord interaction tokens are persisted in execution history; and global variables are stored unencrypted and fully readable by team members. An attacker with database read access, backup access, log access, or workflow/team membership can extract these secrets and use them to execute workflows as the legitimate owner.
Affected products
- heym heym prior to 0.0.91
Timeline
- 2026-08-15: disclosed: GitHub security advisory GHSA-6x65-w7q7-wg93 published
- 2026-09-27: patched: Fix released in version 0.0.91
- 2026-09-27: advisory: NVD entry published as CVE-2026-100862