dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-45058

CRITICAL · 9.4 CVSS v4.0 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
electerm is an open-sourced terminal/ssh/sftp/telnet/serialport/RDP/VNC/Spice/ftp client. In 3.8.8 and earlier, there is persistent local-pty code execution via imported bookmarks or compromised sync targets. Affects users who import bookmark JSON files or who have electerm sync configured (gist/WebDAV). The attacker can inject exec* fields or global config to cause remote code to run when a bookmark is opened or when sync is applied.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

electerm versions 3.8.8 and earlier contain a code execution vulnerability where malicious bookmark JSON files or compromised sync targets (gist/WebDAV) can inject exec* fields or modify global config. When users open imported bookmarks or apply synced data, the injected commands execute in the local pty context, allowing arbitrary code execution.

MitigationAvoid importing bookmark JSON from untrusted sources and ensure sync targets (gist/WebDAV) are secured. Update to a version beyond 3.8.8 when available and implement validation of all imported bookmark and sync data fields before execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed electerm version
    Run electerm and navigate to Help > About, or check the version via the application's metadata/package information. Compare against the affected range: versions 3.8.8 and earlier are vulnerable.
    Affected if The installed version is 3.8.8 or earlier.
  2. Determine if bookmark JSON import is used
    Review whether the electerm instance has imported bookmarks from external JSON files, particularly from untrusted or third-party sources.
    Affected if Bookmark JSON files from untrusted sources have been imported into the application.
  3. Inspect bookmark files for exec* fields
    Examine any imported or stored bookmark JSON files for unexpected fields containing exec, execSync, spawn, or similar execution-related keywords that were not intentionally added by the user.
    Affected if Bookmark JSON files contain injected exec*, spawn, or similar command execution fields.
  4. Check if sync to gist or WebDAV is enabled
    Review electerm settings or configuration for active sync connections to external gist or WebDAV targets, particularly those that may be shared or untrusted.
    Affected if Sync to gist or WebDAV is enabled and the sync target could be compromised or untrusted.
  5. Inspect global config for unauthorized modifications
    Review the global configuration file or settings for any unexpected modifications to exec*, command execution, or shell settings that were not personally configured.
    Affected if Global config contains unauthorized exec* fields or command execution settings.

A user is affected if they are running electerm version 3.8.8 or earlier AND have imported bookmark JSON from untrusted sources or use sync to potentially compromised gist/WebDAV targets.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid importing bookmark JSON from untrusted sources and ensure sync targets (gist/WebDAV) are secured. Update to a version beyond 3.8.8 when available and implement validation of all imported bookmark and sync data fields before execution.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45058 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45058 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data