# CVE-2026-45226: Heym < 0.0.21 Authorization Bypass in Workflow Execution

> Authenticated attackers can execute arbitrary victim workflows by referencing their UUIDs, exposing outputs and triggering unintended side effects.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/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:** 12 May 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-p953-2g5p-33c5

## What is CVE-2026-45226?

CVE-2026-45226 is a high-severity missing authorization vulnerability in heymrun heym, published on 12 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Heym before 0.0.21 contains an authorization bypass vulnerability in workflow execution that allows authenticated users to execute arbitrary workflows by referencing victim workflow UUIDs without proper access validation. Attackers can create workflows with execute nodes or agent subWorkflowIds pointing to victim workflow UUIDs to load and execute those workflows under attacker-controlled execution paths, exposing victim workflow outputs and triggering workflow nodes with unintended side effects.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-45226 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45226 is a high-severity missing authorization vulnerability in heymrun heym, published on 12 May 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-45226 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-45226/ (Markdown: https://insights.sbomify.com/CVE-2026-45226/index.md)
```

## Sources

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

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