---
id: CVE-2026-100860
title: >-
  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)
summary: >-
  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 creden…
severity: medium
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'
cwe:
  - CWE-636
vendor: heymrun
product: heym
affected:
  - heym < 0.0.105
published: '2026-09-27'
updated: '2026-09-27'
sourceUpdated: '2026-09-27T02:17:25.663'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-100860'
references:
  - url: 'https://github.com/heymrun/heym/security/advisories/GHSA-fmpw-hj3m-xvj6'
    label: disclosure@vulncheck.com
  - url: >-
      https://www.vulncheck.com/advisories/heym-before-0.0.105-authentication-bypass-via-redis-node
    label: disclosure@vulncheck.com
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-27T02:41:45.581Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.