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.
heym before 0.0.105 Authentication Bypass via Redis Node
Problem type
Affected products
heymrun
< 0.0.105 - AFFECTED
0.0.105 - UNAFFECTED
References
https://github.com/heymrun/heym/security/advisories/GHSA-fmpw-hj3m-xvj6
https://www.vulncheck.com/advisories/heym-before-0.0.105-authentication-bypass-via-redis-node
GitHub Security Advisories
GHSA-v44j-74xg-9j2q
heym before 0.0.105 does not act on the result of the credential authorization lookup in the...
https://github.com/advisories/GHSA-v44j-74xg-9j2qheym 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.
https://github.com/heymrun/heym/security/advisories/GHSA-fmpw-hj3m-xvj6
https://nvd.nist.gov/vuln/detail/CVE-2026-100860
https://www.vulncheck.com/advisories/heym-before-0.0.105-authentication-bypass-via-redis-node
https://github.com/advisories/GHSA-v44j-74xg-9j2q
JSON source
https://cveawg.mitre.org/api/cve/CVE-2026-100860Click to expand
{
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"cveMetadata": {
"cveId": "CVE-2026-100860",
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"dateUpdated": "2026-09-27T01:28:50.589Z",
"dateReserved": "2026-09-27T00:20:03.854Z",
"datePublished": "2026-09-27T01:28:50.589Z",
"state": "PUBLISHED"
},
"containers": {
"cna": {
"providerMetadata": {
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck",
"dateUpdated": "2026-09-27T01:28:50.589Z"
},
"datePublic": "2026-09-03T00:00:00.000Z",
"title": "heym before 0.0.105 Authentication Bypass via Redis Node",
"descriptions": [
{
"lang": "en",
"value": "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."
}
],
"affected": [
{
"vendor": "heymrun",
"product": "heym",
"defaultStatus": "unaffected",
"versions": [
{
"version": "0",
"status": "affected",
"versionType": "semver",
"lessThan": "0.0.105"
},
{
"version": "0.0.105",
"status": "unaffected",
"versionType": "semver"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"lang": "en",
"description": "Not Failing Securely ('Failing Open')",
"cweId": "CWE-636",
"type": "CWE"
}
]
}
],
"references": [
{
"url": "https://github.com/heymrun/heym/security/advisories/GHSA-fmpw-hj3m-xvj6",
"name": "GitHub Security Advisory (GHSA-fmpw-hj3m-xvj6)",
"tags": [
"vendor-advisory"
]
},
{
"url": "https://www.vulncheck.com/advisories/heym-before-0.0.105-authentication-bypass-via-redis-node",
"name": "VulnCheck Advisory: heym before 0.0.105 Authentication Bypass via Redis Node",
"tags": [
"third-party-advisory"
]
}
],
"metrics": [
{
"format": "CVSS"
},
{
"format": "CVSS",
"cvssV3_1": {
"version": "3.1",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"attackVector": "LOCAL",
"attackComplexity": "LOW",
"privilegesRequired": "LOW",
"userInteraction": "NONE",
"scope": "UNCHANGED",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"availabilityImpact": "NONE",
"baseScore": 5.5,
"baseSeverity": "MEDIUM"
}
}
],
"credits": [
{
"lang": "en",
"value": "fatihkaratash",
"type": "reporter"
}
]
}
}
}