CVE-2026-100860

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-09-27. A secondary CVSS source baseline 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

heym before 0.0.105 does not act on the result of the credential authorization lookup in the Redis workflow node (backend/app/services/node_execution/nodes/redis_node.py). When _get_accessible_credential returns None — because the credential ID does not exist or the caller is not authorized to use it — the node treats the lookup failure as an empty configuration and falls back to defaults, connecting to localhost:6379 with no password and executing the requested operation there. The same fallback occurs when an accessible credential has an empty config or no redis_host value. An authenticated workflow author who supplies a credential ID they do not own, or one that was deleted, therefore obtains a read/write connection to whatever Redis is listening on the backend's loopback interface instead of an error. Impact depends on the deployment: the stock docker-compose.yml ships no Redis, in which case the flaw surfaces as a misleading connection error rather than data exposure.

CVSS v3
5.5
EG Score
5.5MEDIUMhigh confidence
EG Risk
41
EG Risk 41/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 27, 2026

Last Modified

September 28, 2026

Advisory Details (2)

Auto-updated Sep 27, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

heym before 0.0.105 Authentication Bypass via Redis Node | Advisories | VulnCheck

https://www.vulncheck.com/advisories/heym-before-0.0.105-authentication-bypass-via-redis-node
github Patch Available🟡 PoC Available

Redis node connects to localhost:6379 when the credential is missing or not accessible · Advisory · heymrun/heym · GitHub

https://github.com/heymrun/heym/security/advisories/GHSA-fmpw-hj3m-xvj6

Vendor Advisories for CVE-2026-100860(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 23× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 00:22 UTCEG score recompute
  2. 2026-10-05 00:21 UTCGHSA enrichment
  3. 2026-10-04 23:21 UTCEPSS rescore
  4. 2026-10-04 00:18 UTCEG score recompute
  5. 2026-10-04 00:18 UTCGHSA enrichment
  6. 2026-10-03 14:25 UTCEPSS rescore
  7. 2026-10-03 00:17 UTCEG score recompute
  8. 2026-10-03 00:17 UTCGHSA enrichment
  9. 2026-10-02 00:16 UTCEG score recompute
  10. 2026-10-02 00:16 UTCGHSA enrichment
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-10-01 00:15 UTCEG score recompute
  13. 2026-10-01 00:15 UTCGHSA enrichment
  14. 2026-09-30 15:02 UTCEPSS rescore
  15. 2026-09-29 23:47 UTCEG score recompute
  16. 2026-09-29 23:47 UTCGHSA enrichment
  17. 2026-09-29 15:20 UTCEPSS rescore
  18. 2026-09-28 21:13 UTCGHSA enrichment
  19. 2026-09-28 17:38 UTCEG score recompute
  20. 2026-09-28 17:38 UTCGHSA enrichment
  21. 2026-09-28 16:34 UTCEG score recompute
  22. 2026-09-28 16:34 UTCGHSA enrichment
  23. 2026-09-28 13:50 UTCEPSS rescore
  24. 2026-09-28 02:37 UTCEG score recompute
  25. 2026-09-28 02:37 UTCGHSA enrichment
Show 3 more
  1. 2026-09-27 02:36 UTCEG score recompute
  2. 2026-09-27 01:52 UTCEG score recompute
  3. 2026-09-27 01:49 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100860?
CVE-2026-100860 is a medium vulnerability published on September 27, 2026. heym before 0.0.105 does not act on the result of the credential authorization lookup in the Redis workflow node (backend/app/services/nodeexecution/nodes/redisnode.py). When getaccessiblecredential returns None — because the credential ID does not exist or the caller is not authorized to use it —…
When was CVE-2026-100860 disclosed?
CVE-2026-100860 was first published on September 27, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100860 actively exploited?
CVE-2026-100860 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100860?
CVE-2026-100860 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100860?
A fix for CVE-2026-100860 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100860 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-100860

Explore →

Is Your Infrastructure Affected by CVE-2026-100860?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs