dbcve.org
ElectermApplication · Electerm Project

CVE-2026-43942

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-08
Fix available
A fix is available. Upgrade to after 3.8.15 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 versions 3.8.15 and prior, the getConstants() IPC handler in src/app/lib/ipc-sync.js serialises the entire process.env object and sends it to the renderer. The data is stored as window.pre.env and is accessible from any JavaScript running in the renderer (e.g., via the DevTools console or a compromised webview context). An attacker who achieves any JavaScript execution within the renderer can trivially exfiltrate these secrets to a remote server, leading to cloud account compromise, supply chain attacks, and lateral movement. At time of publication, there are no publicly available patches.

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

The getConstants() IPC handler in electerm versions 3.8.15 and prior serializes the entire process.env object and sends it to the renderer process, where it becomes accessible as window.pre.env. Any JavaScript executing in the renderer (including via DevTools or compromised webviews) can access these environment variables, which typically contain secrets, API keys, tokens, and credentials.

MitigationUntil a patch is released, avoid running electerm with sensitive credentials in the environment variables. The vendor should modify getConstants() to selectively expose only non-sensitive configuration values instead of the entire process.env object.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ElectermApplication
Affected:<= 3.8.15

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 electerm installed version
    Run 'electerm --version' or check the application's About/Version info to determine the installed version number
    Affected if The installed version is 3.8.15 or any version prior to 3.8.15 (e.g., 3.8.14, 3.8.10, etc.)
  2. Inspect getConstants IPC handler source
    Examine the electerm source code for the getConstants() function in the IPC handlers; verify if it returns the full process.env object without filtering
    Affected if The getConstants() function returns the complete process.env object rather than selective non-sensitive configuration
  3. Verify window.pre.env exposure in renderer
    Open the electerm application, open browser DevTools (F12), and check if window.pre.env is defined and contains environment variables
    Affected if window.pre.env exists and displays process.env properties such as PATH, USER, HOME, or any custom environment variables set in the system

A user is affected if electerm version is 3.8.15 or prior AND the window.pre.env object is accessible in the renderer, exposing the full process.env contents including any secrets or credentials present in the environment.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.8.15
Interim mitigation

Until a patch is released, avoid running electerm with sensitive credentials in the environment variables. The vendor should modify getConstants() to selectively expose only non-sensitive configuration values instead of the entire process.env object.

Recommended fix High confidence
  1. Monitor the official electerm GitHub repository (github.com/electerm/electerm) for security updates or patches addressing the process.env exposure vulnerability.
  2. Consider reaching out to the project maintainers to inquire about the status of a fix.
  3. If using electerm in a security-sensitive environment, implement network segmentation or additional monitoring to detect any unauthorized exfiltration attempts.
  4. Review application logs and network traffic for indicators of compromise related to this vulnerability.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Electerm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-43942 — 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-43942 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