Skip to main content
Menu
CVEs

CVE

Heym remote code execution via Playwright step-mode fields

Affects heym 0.0.141 and earlier, where the Playwright node runs in its default step mode with custom-code mode disabled. Fixed in 0.0.142.

CVE-2026-130753EUVD-2026-129150Published Updated Summary written by a model

8.7HighCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 0.0.142
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. heym version 0.0.141 or earlier Playwright node running in step mode, which is enabled by default Custom-code mode disabled (the default)

Summary

A logged-in, non-admin user can reach this flaw remotely over the network and execute arbitrary Python as root inside the heym backend container. It happens because the Playwright step-mode node inserts workflow values directly into generated Python source, so crafted step field values can break out of string literals.

Original description

heym before 0.0.142 contains a remote code execution vulnerability in the Playwright step-mode node where _resolve_expressions_in_code substitutes workflow values directly into generated Python source. Authenticated non-admin users can craft step field values that break out of string literals to execute arbitrary Python as root inside the backend container.

Who should check

Teams running heym v0.0.141 or earlier with Playwright step-mode nodes whose string fields or $-references take workflow values.

Not fixed by: Calling ast.parse on the generated script does not fix it.

“The Playwright automation node in "step" mode (enabled by default)”

github.com

cve.now Index

33Pcve.now Index 33 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.7/10CVSS 8.7, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 40 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    heym version 0.0.141 or earlier Playwright node running in step mode, which is enabled by default Custom-code mode disabled (the default)
  • Upgrade to a fixed version: 0.0.142.

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-130753 (heym before 0.0.142 Authenticated RCE via Playwright Step-Mode String Fields), 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-130753 (entry last updated 2026-11-18):
Affected:
- heymrun heym: from 0.0.141, fixed in 0.0.142
Fixed versions: 0.0.142.
Conditions (all must be true for the bug to be hit):
- heym version 0.0.141 or earlier (source: https://github.com/heymrun/heym/security/advisories/GHSA-7qrv-28q7-w8rj)
- Playwright node running in step mode, which is enabled by default (source: https://github.com/heymrun/heym/security/advisories/GHSA-7qrv-28q7-w8rj)
- Custom-code mode disabled (the default) (source: https://github.com/heymrun/heym/security/advisories/GHSA-7qrv-28q7-w8rj)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130753 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130753 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-7qrv-28q7-w8rj
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-130753
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-130753"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • heymrun heym

    From 0.0.141 · fixed in 0.0.142

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · heymrun/heym · Advisory GHSA-7qrv-28q7-w8rj
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130753
RecordNVD · CVE-2026-130753

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130753

Is CVE-2026-130753 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

An authenticated user can get arbitrary Python executed as root inside the heym backend container through string fields in the Playwright node's step mode.Source: github.com

Which versions are affected by CVE-2026-130753?

heym: from 0.0.141 before 0.0.142.Source: cve.now feed data

Am I affected, and how do I check?

Versions 0.0.141 and earlier are affected in the default configuration, where Playwright step mode is enabled and custom-code mode is disabled. To check a deployment, compare the installed heym version against 0.0.142 and confirm whether custom-code mode is enabled.Source: github.com

How do I fix CVE-2026-130753?

Upgrade heym to version 0.0.142 or later, which is the fixed version.Source: github.com

More CVEs