CVSS 3.1
6.5 mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCVE-2026-67540 Heym - Horizontal IDOR: get-by-id on workflow/node templates skips the visibility check the list path enforces
Medium (6.5) in heymrun heym. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
Heym builds and runs agentic systems and business-process automations on self-hosted infrastructure. Prior to version 0.0.70, get_workflow_template / get_node_template fetches a template by ID with no visibility / author / shared_with predicate, so any authenticated user can read (and use) any other tenant's private (visibility=specific_users) template — including its full node/edge graph and the email addresses it was shared with. The list endpoint enforces visibility correctly; the single-item get/use paths do not. This issue has been patched in version 0.0.70.
Severity
- EPSS
- 0.4% estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-639 Authorization Bypass Through User-Controlled Key
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-67540 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67540?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67540?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-67540 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-67540)
HTML:
<a href="https://cve.bz/cve/CVE-2026-67540"><img src="https://cve.bz/cve/badge/CVE-2026-67540.svg" alt="CVE-2026-67540"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| heymrun heym | < 0.0.70 |
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.