# CVE-2026-110873: Heym 0.0.55 before 0.0.121 Credential Theft via error_workflow_id Field

> Shared collaborators can escalate privileges to exfiltrate owner credentials by manipulating workflow error handling fields.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-c3f4-2mrj-jfqr, GHSA-wh8c-wx4r-x3rj

## What is CVE-2026-110873?

CVE-2026-110873 is a high-severity vulnerability in heymrun heym, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-110873 being exploited?

There is no known exploitation of CVE-2026-110873 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110873 is a high-severity vulnerability in heymrun heym, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110873 in the wild and no public exploit code.

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-110873/ (Markdown: https://insights.sbomify.com/CVE-2026-110873/index.md)
```

## Sources

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

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