# CVE-2026-67543: Heym Unsandboxed skill code execution: skills run via a local backend subprocess without the Docker isolation that Python tools mandate

Status: published. Published: 2026-11-11. Updated: 2026-11-11.

Heym builds and runs agentic systems and business-process automations on self-hosted infrastructure. Prior to version 0.0.70, heym hardens one untrusted-code path but not its sibling. The Python tool executor (python_tool_executor.py) treats user code as untrusted and mandates a Docker sandbox (no network, read-only fs, non-root, no docker socket), failing closed. The skill executor (skill_python_executor.py) runs skill Python via a local backend subprocess with no Docker isolation — only a 512 MB RLIMIT and a 7-key env denylist — so a skill executes inside the backend execution context, with filesystem access, network egress, and non-denylisted environment variables that should not be exposed to untrusted/shared skills. In the shipped Docker config (backend runs as root + /var/run/docker.sock mounted), this escalates to host root. This issue has been patched in version 0.0.70.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- heymrun / heym: < 0.0.70 (affected). Source: CNA: GitHub_M

## Severity and prioritization

- CVSS 3.1: 8.8 (high); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; source: CNA: GitHub_M

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-94, CWE-269

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/heymrun/heym/security/advisories/GHSA-hcv7-mg77-pg73 (CNA: GitHub_M; x_refsource_CONFIRM)

- https://github.com/heymrun/heym/commit/2155057f4153a1e3a7b789d104f7fa96e92964e5 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/heymrun/heym/commit/28bb2901e4dea128ac493f67ee9478d230b7a3d7 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/heymrun/heym/releases/tag/0.0.70 (CNA: GitHub_M; x_refsource_MISC)

## Provenance

- CNA: GitHub_M: https://www.cve.org/CVERecord?id=CVE-2026-67543; retrieved 2026-11-11; source updated 2026-11-11

Revision: 4fcfa6adfd8867aa5df02b420998c0a87284fca089c2b94ed82d21a54aea020d

Canonical: https://y2.dev/cve/CVE-2026-67543

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.