Quick answers
- Is CVE-2026-101050 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-101050 being exploited in the wild.
- How severe is CVE-2026-101050?
- Medium severity, with a CVSS score of 6.5, published 27 September 2026.
- Which products and versions are affected?
- Heymrun Heym before 0.0.53.
- Is there a fix for CVE-2026-101050?
- A patch was published on 2026-06-26. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-101050 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-101050?
- 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 Telegram webhook endpoint skips X-Telegram-Bot-Api-Secret-Token verification when credential_id is absent or secret_token is empty, allowing unauthenticated POST requests to trigger workflows. An attacker with knowledge of the public webhook URL can inject forged Telegram updates to execute arbitrary workflow actions on attacker-controlled input. The fix (version 0.0.53) enforces fail-closed behavior by rejecting such requests with a 400 error.
Affected products
- heymrun Heym before 0.0.53
Timeline
- 2026-06-26: disclosed
- 2026-06-26: patched