Skip to main content
VulnerabilityPublished

CVE-2026-43942: Electerm's full process.env exposed to renderer via window.pre.env

Affects electermSource GCVE Database

0
Authoritative record:CVE-2026-43942· Medium 5.5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 27 Oct 2026, 03:26 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
npmelectermAffected
  • <=3.8.15
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a patch is released, users should avoid launching Electerm with sensitive environment variables set by clearing secrets before starting the application. Do not install plugins from untrusted sources and audit installed plugins for network access. Lock down the renderer context by disabling the remote debugging port and avoid pasting untrusted code into the DevTools console.

Description

Electerm versions up to 3.8.15 expose the entire process.env environment variables to the renderer process via window.pre.env. This includes sensitive secrets such as AWS keys, GitHub tokens, API keys, and internal credentials. Any JavaScript execution in the renderer context, including through malicious plugins or XSS, can access and exfiltrate these secrets. The exposure is visible even without code execution by opening the Info modal, requiring local access. No patch is currently available.

References

Community reviews

Loading reviews…