Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-101050 – Authentication Bypass via Telegram Webhook – Heym before 0.0.53

Be the first to know when new zero-days emerge:

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-Token header when a workflow’s Telegram trigger node has no credential_id configured, or when the configured secret_token value 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_id and a non-empty secret_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.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge