# CVE-2026-100860: heym before 0.0.105 Authentication Bypass via Redis Node

> Authenticated users can bypass credential checks to access local Redis instances, potentially reading or modifying data if Redis is deployed.

- **Severity:** Medium 6.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-fmpw-hj3m-xvj6, GHSA-v44j-74xg-9j2q

## What is CVE-2026-100860?

CVE-2026-100860 is a medium-severity authentication bypass vulnerability in heymrun heym, published on 27 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-636 (Not Failing Securely)

## Which versions are affected by CVE-2026-100860?


## How do I fix CVE-2026-100860?

No fix has been published for CVE-2026-100860 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-100860 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100860 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100860 and fix it if it is affected.

What it is: CVE-2026-100860 is a medium-severity authentication bypass vulnerability in heymrun heym, published on 27 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100860 exists.

Affected product: heymrun heym. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100860/ (Markdown: https://insights.sbomify.com/CVE-2026-100860/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100860
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100860
- OSV: https://osv.dev/vulnerability/CVE-2026-100860

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100860/
Summaries are generated and may contain mistakes; the official description above is the record.