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.
References
Configurations
No configuration.
History
28 Sep 2026, 17:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/heymrun/heym/security/advisories/GHSA-fmpw-hj3m-xvj6 - |
27 Sep 2026, 02:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-09-27 02:17
Updated : 2026-09-28 20:57
NVD link : CVE-2026-100860
Mitre link : CVE-2026-100860
CVE.ORG link : CVE-2026-100860
JSON object : View
Products Affected
No product.
CWE
CWE-636
Not Failing Securely ('Failing Open')