Quick answers
- Is CVE-2026-100859 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100859 being exploited in the wild.
- How severe is CVE-2026-100859?
- Medium severity, with a CVSS score of 6.5, published 27 September 2026.
- Which products and versions are affected?
- Heymrun Heym before 0.0.106.
- Is there a fix for CVE-2026-100859?
- A patch was published on 2026-09-05: Fix released in version 0.0.106 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100859 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-100859?
- Check whether you run Heymrun 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
The POST /api/credentials/test endpoint improperly validates configuration overrides, allowing an authenticated collaborator to merge caller-supplied config (including a malicious base_url) with a shared credential before testing the connection. The endpoint then sends the decrypted credential's authentication secret to the attacker-specified URL via integrations like Jira and Supabase. An attacker must have legitimate shared access to a credential and network access to call the endpoint.
Affected products
- heymrun Heym before 0.0.106
Timeline
- 2026-09-05: disclosed: GitHub security advisory published
- 2026-09-05: patched: Fix released in version 0.0.106