Heym local file read via Playwright navigate step
Heym versions before 0.0.148 are exposed when a workflow uses a Playwright node's navigate step, and step-based scripts run in the backend container. CVSS scores it 7.1 High. Fixed in 0.0.148.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.0.148
- Who is exposed
- Specific setups only
Summary
Written by a model
Heym before 0.0.148 passes Playwright navigate-step URLs to page.goto() without validating the scheme and runs step-based scripts inside the backend container. A signed-in user who can run workflows can navigate to file:// URLs and use getText to read known-path files such as the Kubernetes ServiceAccount token or Docker secrets.
Who should check
Teams running Heym 0.0.147 or earlier, including Kubernetes (Helm or deploy/kubernetes) and Docker deployments that use Playwright workflows
“Affecting heym < 0.0.148”
What to do
Check whether your setup matches what the bug needs.
Heym version before 0.0.148 A workflow uses a Playwright node with a navigate step Step-based Playwright scripts run inside the backend container rather than the sandboxUpgrade to a fixed version: 0.0.148.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134360 (Heym before 0.0.148 Local File Read via Playwright Navigate Step), 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-134360 (entry last updated 2026-11-21):
Affected:
- heymrun heym: fixed in 0.0.148
Fixed versions: 0.0.148.
Conditions (all must be true for the bug to be hit):
- Heym version before 0.0.148 (source: https://www.vulncheck.com/advisories/heym-before-0.0.148-local-file-read-via-playwright-navigate-step)
- A workflow uses a Playwright node with a navigate step (source: https://github.com/heymrun/heym/security/advisories/GHSA-hmfh-wpg2-vff4)
- Step-based Playwright scripts run inside the backend container rather than the sandbox (source: https://github.com/heymrun/heym/security/advisories/GHSA-hmfh-wpg2-vff4)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134360 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134360 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-hmfh-wpg2-vff4
- https://www.vulncheck.com/advisories/heym-before-0.0.148-local-file-read-via-playwright-navigate-step
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-134360
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-134360"}.Affected versions
- heymrun heymfixed in 0.0.148
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · heymrun/heym · Advisory GHSA-hmfh-wpg2-vff4 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134360 |
| Record | NVD · CVE-2026-134360 |
| Other links 1 | |
| Link | vulncheck.com · advisories/heym-before-0.0.148-local-file-read-via-playwright-navigate-step |
Questions about CVE-2026-134360
Is CVE-2026-134360 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: cve.now feed data
What does this mean?
The Playwright node's navigate step passes its URL straight to page.goto() with no check on the scheme, so file:// URLs are accepted. A signed-in user can then use getText to read known-path files in the backend container, such as the Kubernetes ServiceAccount token or Docker secrets.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134360?
heym: before 0.0.148.
Source: cve.now feed data
Am I affected, and how do I check?
Heym versions before 0.0.148 are affected when a workflow uses a Playwright node with a navigate step and step-based Playwright scripts run inside the backend container rather than the sandbox. To check, look at the installed Heym version and whether any workflow includes a Playwright navigate step.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134360?
Upgrade Heym to version 0.0.148 or later, which is the listed fixed version for this vulnerability.
Source: vulncheck.com, github.com
Related
- CVE-2026-67546Heym: Command execution via POST /api/mcp/fetch-tools stdio transport: supplied command is spawned before MCP validation
- CVE-2026-67544Heym: Playwright Custom Code Backend RCE via `playwrightCode` Field
- CVE-2026-67543Heym Unsandboxed skill code execution: skills run via a local backend subprocess without the Docker isolation that Python tools mandate
- CVE-2026-55376heym Python Tool Sandbox Escape
- CVE-2026-130753heym before 0.0.142 Authenticated RCE via Playwright Step-Mode String Fields
- CVE-2026-100865Heym before 0.0.53 Remote Code Execution via eval() Sandbox Escape
No corrections so far. Something wrong on this page? Report an error.