CVE-2026-100861: heymrun heym · Server-Side Request Forgery (SSRF)
Affects heymrun heymSource CVE Database V5
Public exploit available · CVSS 5.3 Medium : upgrade to 0.0.105 as a priority.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% 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
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-09-28.
- Patch
- Available – fixed in 0.0.105
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:LExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 27 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CISA SSVC: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by VulnCheck
, 1 hour before disclosure
CVE published
on cve.org
, t = 0
CISA SSVC assessment
proof of concept public
, 36 hours after disclosure
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 13 Nov 2026.
What to do
Upgrade heymrun heym to 0.0.105.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| heymrunheym | Affected
| Fixed in
|
AI-suggested
Upgrade heym to version 0.0.105 or later, where this vulnerability is fixed. No additional mitigation is required once the official fix is applied.
Description
CVE-2026-100861 is a Server-Side Request Forgery (SSRF) vulnerability in heym versions before 0.0.105. The issue arises because egress guards are not applied to integration services that use credential-supplied base URLs. This allows authenticated users to bypass SSRF protections by configuring credentials to access loopback, private, or cloud-metadata addresses, potentially reading internal service responses.