Summary
CVE-2026-101050 is an authentication bypass vulnerability (CWE-287: Improper Authentication) in Heym, an open-source workflow automation platform, affecting all versions prior to 0.0.53. The flaw lies in how Heym validates the X-Telegram-Bot-Api-Secret-Token header on Telegram webhook trigger endpoints, allowing unauthenticated attackers to submit forged Telegram updates and trigger victim workflows using the workflow owner’s stored credentials. The vulnerability carries a High severity rating (CVSS v4.0 8.3).
Technical details
- Root cause: Heym’s Telegram webhook handler fails to enforce verification of the
X-Telegram-Bot-Api-Secret-Tokenheader when a workflow’s Telegram trigger node has nocredential_idconfigured, or when the configuredsecret_tokenvalue is empty — the verification logic "fails open" instead of rejecting the request. - Trigger conditions: A workflow must expose a Telegram webhook trigger node that is missing a credential ID or has an unset/empty secret token — a state reachable through normal, permitted configuration of the platform.
- Attack vector: Network-based and unauthenticated. An attacker who knows or discovers the public Telegram webhook URL can send crafted HTTP requests mimicking legitimate Telegram Bot API updates, without needing to know any secret token.
- Impact: Forged messages can trigger the victim’s workflow, causing it to execute using the workflow owner’s stored credentials and to act on attacker-controlled input — potentially leading to unauthorized actions, data exposure, or abuse of any integrations/credentials wired into that workflow.
Affected software
- Product: Heym (heymrun/heym workflow automation platform)
- Affected versions: All versions prior to 0.0.53 (version 0 through 0.0.52)
- Fixed version: 0.0.53 and later
Severity
- CVSS v4.0 Base Score: 8.3 (High) —
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N - CVSS v3.1 Base Score (as also reported): 6.5 (Medium) —
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
Mitigation and recommended actions
- Immediate: Upgrade Heym to version 0.0.53 or later, which enforces secret-token verification on Telegram webhook triggers and rejects requests when no credential/secret token is configured.
- If immediate patching is not possible:
- Audit all existing workflows for Telegram webhook trigger nodes and ensure each has a properly configured
credential_idand a non-emptysecret_token. - Restrict or firewall access to public webhook endpoints where feasible, limiting exposure to trusted Telegram infrastructure IP ranges.
- Disable or pause any Telegram-triggered workflows that grant access to sensitive credentials or downstream systems until the fix is applied.
- After upgrading, be aware that trigger nodes without configured credentials will begin rejecting requests, which is an intentional breaking change; review workflow configurations accordingly.
- Audit all existing workflows for Telegram webhook trigger nodes and ensure each has a properly configured

