Skip to main content
VulnerabilityPublished Updated

CVE-2026-100858: heymrun heym · Server-Side Request Forgery (SSRF)

Affects heymrun heymSource CVE Database V5

0
Compare

Public exploit available · CVSS 7.6 High : upgrade to 0.0.109 as a priority.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
Proof of concept is public or traded
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-09-30.

Patch
Available – fixed in 0.0.109
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/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

    , 3 days 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 10 Nov 2026.

What to do

Upgrade heymrun heym to 0.0.109.

Affected software

ProductAffectedFixed in
heymrunheymAffected
  • <0.0.109
Fixed in
  • 0.0.109

AI-suggested

Upgrade heym to version 0.0.109 or later, where this SSRF vulnerability is fixed. No other mitigation is required as the fix addresses the root cause by enforcing proper SSRF egress protection on the affected workflow nodes.

Description

heym versions before 0.0.109 contain a server-side request forgery (SSRF) vulnerability in the Slack, Discord, and Crawler workflow nodes. These nodes make HTTP requests using URLs from user-created credentials without proper SSRF egress protection. This allows any registered user to cause the backend to access internal network endpoints and return their full response in the workflow output.

References

Community reviews

Loading reviews…