VulnerabilityPublished 27 Sep 2026Updated 28 Sep 2026

CVE-2026-100860: heymrun heym · Failing Open

Affects heymrun heymSource CVE Database V5

Compare

Public exploit available · CVSS 6.8 Medium : upgrade to 0.0.105 as a priority.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 4.0 base score

6.8Medium

How severe the flaw is on the 0–10 CVSS scale.

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.

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:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation 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

CVE ID reserved
by VulnCheck
27 Sep 202600:20 UTC, 1 hour before disclosure
CVE published
on cve.org
27 Sep 202601:28 UTC, t = 0
CISA SSVC assessment
proof of concept public
28 Sep 202616:04 UTC, 39 hours after disclosure
In Threat Radar
record ingested
26 Oct 202608:08 UTC, 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade heymrun heym to 0.0.105.

Affected software

Product	Affected	Fixed in
heymrunheym	Affected <0.0.105	Fixed in 0.0.105

AI-suggested

Upgrade heym to version 0.0.105 or later, where this issue is fixed. No other mitigation is required as the fix addresses the fallback behavior that causes the vulnerability.

Description

CVE-2026-100860 affects heym versions before 0.0.105. The vulnerability arises because the software does not properly handle failed credential authorization lookups in its Redis workflow node. When a credential ID is invalid, unauthorized, or has an empty configuration, the node falls back to connecting to a local Redis instance on localhost:6379 without authentication, potentially exposing Redis data or functionality. The impact depends on deployment specifics; for example, the default docker-compose setup does not include Redis, resulting only in connection errors rather than data exposure.

Impact

An authenticated workflow author can bypass credential authorization checks and connect to a local Redis instance without authentication, potentially allowing unauthorized read/write operations on Redis data. The actual impact depends on the deployment environment; if no Redis instance is running locally (as in the stock docker-compose setup), the issue manifests as a misleading connection error without data exposure.

Summary

In heym versions prior to 0.0.105, the Redis workflow node fails to securely handle credential authorization lookup failures. Specifically, when the _get_accessible_credential function returns None due to a non-existent or unauthorized credential ID, or when the credential configuration is empty or lacks a redis_host value, the node defaults to connecting to localhost:6379 without a password. This fallback behavior allows an authenticated workflow author who supplies an invalid or unauthorized credential ID to gain read/write access to any Redis instance listening on the backend's loopback interface. The vulnerability is fixed in version 0.0.105.

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2026, 05:28 UTC

Technical details

References

Community reviews

Related threats