Code Injection in actual (CVE-2026-42890)
Summary
Code injection in actual (CVE-2026-42890). Risk of unauthorized operations or information disclosure. Exploitable via actual. Mitigation: upgrade to 26.5.0 or later.
Original description
The description as published by the source.
Actual is an open-source personal finance application. In the macOS desktop application version 25.x (built on Electron 39.2.7), the ELECTRON_RUN_AS_NODE fuse is not disabled, allowing an attacker who can place a file on disk or control command-line arguments to invoke the signed Actual.app binary with the ELECTRON_RUN_AS_NODE=1 environment variable set. This converts the application into a Node.js REPL capable of executing arbitrary code that inherits the application's entitlements and code signature, bypassing macOS Gatekeeper review. Version 26.5.0 patches the issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42890 has been found in actual.
Attackers can target a specific entry point like actual over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade actual to 26.5.0 or later.
If unsure, ask your IT team or search "actual CVE-2026-42890" on the vendor's site.
CVE-2026-42890 (actual) — CWE-94
Attack surface: actual
Patched: 26.5.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in actual. Attackers reach the vulnerable code path via actual.
Check the vendor advisory for the affected versions of actual. Attack surface: actual.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 26.5.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'actual' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'actual' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
actualを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade actual to 26.5.0ステージング環境で 26.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web actualbudget.org