# CVE-2026-109362: Heym v0.0.5 before v0.0.113 Broken Access Control via Workflow Execution Tokens

> Former collaborators can execute workflows using long-lived tokens after access removal, consuming shared credentials and bypassing authorization controls.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-7v8m-98rf-rgvw, GHSA-pwr6-6377-3cgv

## What is CVE-2026-109362?

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

### Official description

Heym v0.0.5 before v0.0.113 contains a broken access control vulnerability that allows former collaborators to keep executing JWT-auth workflows by reusing scoped workflow:execute tokens after share removal. Attackers can mint a token with a TTL up to 10 years, which the owner cannot list or revoke, and repeatedly run the workflow consuming shared credentials.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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


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

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

## Is CVE-2026-109362 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109362 is a medium-severity missing authorization vulnerability in heymrun heym, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109362 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-109362/ (Markdown: https://insights.sbomify.com/CVE-2026-109362/index.md)
```

## Sources

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

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