CVE-2026-45226: Heym < 0.0.21 Authorization Bypass in Workflow Execution
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.
Security readout for executives and security teams
Plain-English summary
Heym before 0.0.21 allowed a logged-in user to run another user's workflow by referencing that workflow's UUID. This could expose workflow outputs and trigger actions the victim did not intend. The issue requires authentication, but the potential confidentiality and integrity impact is high.
Executive priority
Treat as a high-priority upgrade for any shared or production Heym deployment. The risk is not unauthenticated internet takeover, but a logged-in user may access or trigger another user's workflow, creating data exposure and operational side-effect risk.
Technical view
The flaw is CWE-863 authorization bypass in workflow execution. Authenticated attackers could reference victim workflow UUIDs through execute-node or agent subWorkflowId paths, causing Heym to load and execute workflows without proper access validation. CVSS v4.0 is 7.6 high, with low privileges required and no user interaction.
Likely exposure
Exposure is likely limited to organizations running heymrun Heym before version 0.0.21, especially multi-user deployments where workflow UUIDs may be discoverable or leaked. The provided sources do not identify affected hosted services, distributions, or downstream products beyond Heym.
Exploitation context
The source bundle says exploitation requires an authenticated user and knowledge or referenceability of victim workflow UUIDs. CISA KEV is false in the provided data, and no cited source in the bundle states active exploitation in the wild.
Researcher notes
Focus review on workflow-loading authorization boundaries, especially execute nodes and agent subWorkflowId handling. Avoid assuming broader product exposure than Heym before 0.0.21. Public evidence supports a patch, high severity, and authenticated exploitation conditions, but not active exploitation.
Mitigation direction
Upgrade Heym to version 0.0.21 or later.
Review the v0.0.21 release notes and patch commit.
Restrict Heym access to trusted users until upgraded.
Review vendor guidance for any additional hardening steps.
Audit workflows for cross-user UUID references before and after upgrade.
Validation and detection
Inventory deployed Heym versions and identify any below 0.0.21.
Confirm the patch commit or v0.0.21 release is present.
Review workflow execution logs for users invoking workflows they do not own.
Verify authorization checks occur before loading referenced workflow UUIDs.
Check for unexpected workflow side effects or exposed outputs.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-863 · source CWE mapping
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.