Vulnerability in electerm (CVE-2026-45353)
Summary
Vulnerability in electerm (CVE-2026-45353). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.9.0 or later.
Original description
The description as published by the source.
electerm is an open-sourced terminal/ssh/sftp/telnet/serialport/RDP/VNC/Spice/ftp client. From 3.0.6 to 3.8.8, This vulnerability is fixed in 3.9.0.
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-45353 has been found in electerm.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade electerm to 3.9.0 or later.
If unsure, ask your IT team or search "electerm CVE-2026-45353" on the vendor's site.
CVE-2026-45353 (electerm) — CWE-732 / CVSS v3 7.8
Attack vector: local / no user interaction
Patched: 3.9.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.
A vulnerability (CWE-732) exists in electerm.
Check the vendor advisory for the affected versions of electerm.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 3.9.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 '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.9.0ステージング環境で 3.9.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
- patch github.com
- web github.com