Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sun, 27 Sep 2026 04:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Heymrun
Heymrun heym |
|
| Vendors & Products |
Heymrun
Heymrun heym |
Sun, 27 Sep 2026 02:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | heym before 0.0.105 Authentication Bypass via Redis Node | |
| Weaknesses | CWE-636 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-09-27T01:28:50.589Z
Reserved: 2026-09-27T00:20:03.854Z
Link: CVE-2026-100860
No data.
Status : Received
Published: 2026-09-27T02:17:25.663
Modified: 2026-09-27T02:17:25.663
Link: CVE-2026-100860
No data.
OpenCVE Enrichment
Updated: 2026-09-27T04:15:08Z
-
CWE-636
Not Failing Securely ('Failing Open')