Skip to main content
VulnerabilityPublished

CVE-2026-100865: Heym before 0.0.53 contains multiple independent vulnerabilities

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-100865· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 0.0.53 soon.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.0.53
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 27 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CISA SSVC: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by VulnCheck

    , 1 hour before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    proof of concept public

    , 36 hours after disclosure

  4. In Threat Radar

    record ingested

    , 29 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade heym to 0.0.53.

Affected software

ProductAffectedFixed in
heymrunheymAffected
  • <0.0.53
Fixed in
  • 0.0.53

AI-suggested

If you cannot patch yet, restrict access to workflow editing and template import features to trusted users only, ensure webhook credentials are properly configured and not left empty, and monitor for suspicious OAuth client registrations. Avoid exposing the database to unauthorized access to prevent token theft.

Description

Heym versions before 0.0.53 contain multiple independent vulnerabilities including arbitrary code execution via unsandboxed Python eval(), insecure webhook signature verification allowing unauthenticated workflow triggers, improper OAuth redirect URI validation enabling authorization code theft and script execution, and plaintext storage of sensitive tokens that could be used to impersonate users. These issues collectively pose high risk to confidentiality, integrity, and availability of the system.

References

Community reviews

Loading reviews…