Skip to main content
VulnerabilityPublished Updated

CVE-2026-45226: heymrun heym · Incorrect Authorization

Affects heymrun heymSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.6 High : upgrade to 0.0.21 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.0.21
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade heymrun/heym and heym to 0.0.21.

Affected software

ProductAffectedFixed in
heymrunheymAffected
  • <0.0.21
Fixed in–
GitHubheymrun/heympkg:github/heymrun/heymOther threatsAffected
  • <0.0.21
Fixed in
  • 0.0.21
GitHubheympkg:github/heymOther threatsAffected
  • <0.0.21
Fixed in
  • 0.0.21

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict authenticated user permissions to minimize risk and monitor for suspicious workflow execution activity related to unauthorized UUID references.

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.

References

Community reviews

Loading reviews…