Path Traversal in electerm (CVE-2026-43940)
Summary
Path traversal in electerm (CVE-2026-43940). Successful exploitation can lead to full system takeover. Exploitable via runWidget. Mitigation: upgrade to 3.7.16 or later.
Original description
The description as published by the source.
Impact
The runWidget function in src/app/widgets/load-widget.js constructs a file path by directly concatenating user‑supplied widget identifiers without any sanitisation:
const file = `widget-${widgetId}.js`
const widget = require(path.join(__dirname, file))
Because runWidget is exposed to the renderer process via an asynchronous IPC handler with no input validation, an attacker who achieves JavaScript execution inside the renderer (for example, through a malicious plugin or a cross‑site scripting flaw in the built‑in webview) can abuse a path traversal (../) to load and execute an arbitrary JavaScript file anywhere on the victim’s filesystem. This gives the attacker local code execution with the full privileges of the electerm process, leading to complete system compromise.
Patches
Fixed in version >= 3.7.16
Workarounds
Until a patch is released:
- Do not install or run untrusted plugins.
- Avoid loading arbitrary web content inside electerm’s embedded webview (for example, disable any features that fetch and display remote HTML).
- Run electerm in a sandboxed environment (e.g., with
bubblewrapon Linux, AppArmor/SELinux profiles, or Windows sandboxed app execution) to limit the impact of any code execution.
Resources
- electerm GitHub Repository
- electerm Security Policy
- Vulnerability details originally reported by external resea…
Source: NIST National Vulnerability Database 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-43940 has been found in electerm.
Attackers can target a specific entry point like runWidget over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.4/10.
What to do: upgrade electerm to 3.7.16 or later.
If unsure, ask your IT team or search "electerm CVE-2026-43940" on the vendor's site.
CVE-2026-43940 (electerm) — CWE-22 / CVSS v3 8.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: runWidget / bubblewrap
Patched: 3.7.16 — 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.
Path traversal (CWE-22) exists in electerm. Attackers reach the vulnerable code path via runWidget without authentication.
Check the vendor advisory for the affected versions of electerm. Attack surface: runWidget / bubblewrap.
Severity: High (CVSS 8.4/10). Successful exploitation can lead to full system takeover.
Update to 3.7.16.
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 'electerm' . 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 'electerm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
electermを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade electerm to 3.7.16ステージング環境で 3.7.16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com