Medium 6.5Published Sep 27, 2026

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

Updated under an hour ago (2026-10-19 08:40 UTC)

Does this affect you?

It affects heymrun heym. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for heymrun heym

Exploited in the last 30 days

Heym before 0.0.53 fails to verify the X-Telegram-Bot-Api-Secret-Token header on Telegram webhook endpoints when credential_id is absent or secret_token is empty. Remote unauthenticated attackers can post forged Telegram updates to trigger workflows with the owner's configured credentials and execute actions on attacker-supplied input.

CVSS: 6.5 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
Weakness (CWE): CWE-287
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: VulnCheck
NVD analysis: Deferred
Record last updated: Sep 28, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

heymrun heym heymrun:heym (from the name)	before 0.0.53; 0.0.53 not affected	CNA record

References

https://github.com/heymrun/heym/security/advisories/GHSA-pm6h-x3h5-j38hvendor-advisory
https://github.com/heymrun/heym/commit/341d1012367cd74f85c617e1c98dd49e3fcb5e83patch
https://www.vulncheck.com/advisories/heym-before-0.0.53-authentication-bypass-via-telegram-webhookthird-party-advisory

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.