CVE-2026-109362
5.4MediumPublished 12 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Impact
- Limited impact
- Weakness
- CWE-613
Impact
Former collaborators can persistently execute shared workflows and consume associated credentials even after access is revoked. To do this, they need to have minted long-lived workflow:execute tokens prior to their removal.
Root cause
Workflow execution JWTs lack revocation checks upon collaborator removal, allowing pre-minted tokens with up to 10-year lifespans to remain valid.
Affected systems
Heym v0.0.5 before v0.0.113
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Fix & remediation
Upgrade Heym to version 0.0.113 or later. If patching immediately is not possible, rotate any underlying credentials exposed to the workflow to prevent unauthorized actions.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD 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.