Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.8amended

actual Allows Electron to Run As Node

CVE-2026-42890GHSA-7rvm-xjpp-63r9

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (actual 26.5.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm actual

    Affected
    < 26.5.0
    Fixed in
    26.5.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
4.8 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-42890: 0.13% estimated exploitation activity in the next 30 days; percentile 2.32 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A electron run as node vulnerability was identified in actual (macOS application, version 25.x (Electron 39.2.7)). Vulnerability Type: Electron Run As Node Description ELECTRONRUNASNODE fuse enabled (Electron 39.2.7) — app can be converted to Node.js REPL for arbitrary code execution Impact An attacker who can place a file on disk or control command-line arguments can invoke the signed Actual.app binary with ELECTRONRUNASNODE=1 to execute arbitrary Node.js code inheriting the apps entitlements and code signature. This bypasses macOS Gatekeeper review of the payload: the Node.js script runs as Actual, under Actuals bundle ID and signed identity, and has access to any entitlements the app carries (network, file access, keychain, automation). Combined with any downloader (browser, mail attachment, Slack link) this becomes a signed-binary-abuse primitive on every Mac with Actual installed.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-7rvm-xjpp-63r9

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-7rvm-xjpp-63r9

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-42890

Advisory: actual Allows Electron to Run As Node
IDs: CVE-2026-42890, GHSA-7rvm-xjpp-63r9
Record: https://patchnext.com/advisories/cve-2026-42890 (revision 3, source checked 26 Oct 2026, 12:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: actual 26.5.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm actual: affected < 26.5.0; fixed in 26.5.0

## Suggested inspection (read-only)
- `npm ls actual --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on actual.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-7rvm-xjpp-63r9 (OSV record GHSA-7rvm-xjpp-63r9 lists affected ranges: npm actual >=0 <26.5.0 (fixed))
- Verified: https://github.com/advisories/GHSA-7rvm-xjpp-63r9 (GitHub-reviewed advisory GHSA-7rvm-xjpp-63r9 lists affected ranges: npm actual >=0 <26.5.0)

Commands are suggestions: review each one before running it.

Loading voting…