CVE-2026-43942: Electerm's full process.env exposed to renderer via window.pre.env
Impact 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).
Published May 8, 2026
Affected packages
electerm
- Ecosystem
- npm
- Affected
- <= 3.8.15
- Fixed in
- No patched version yet
- Check
npm ls electerm
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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).
On developer and CI machines, process.env routinely contains secrets such as:
AWS_SECRET_ACCESS_KEY/AWS_SESSION_TOKENGITHUB_TOKEN/NPM_TOKENOPENAI_API_KEY/DOCKER_AUTH- Internal service credentials, API keys, and database URLs
An attacker who achieves any JavaScript execution within the renderer—for example, through a malicious plugin, a cross-site scripting (XSS) flaw, or the terminal hyperlink execution chain—can trivially exfiltrate these secrets to a remote server, leading to cloud account compromise, supply chain attacks, and lateral movement. The exposure is visible even without any code execution by simply opening the "Info" modal in the application, though that requires local access.
Patches
A patch is yet to be available.
Workarounds
Until a patch is released:
- Avoid launching electerm with sensitive environment variables set. Use shell scripts or a dedicated terminal profile that clears secrets before starting the application.
- Do not install plugins from untrusted sources, and audit any installed plugins for network access.
- Keep the renderer context as locked down as possible: disable the remote debugging port, and do not paste untrusted code into the DevTools console.
Resources
- electerm GitHub Repository
- electerm Security Policy
- Vulnerability details originally reported by external researcher (confirmed on v3.7.9, Win10).
Credited to osageling.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-49253
electerm has Path Traversal in Zmodem and Trzsz Download Filename Handling
high7.1Jul 2, 2026CVE-2026-49255
electerm has Command Injection in File System Operations (rmrf, mv, cp)
high8.8Jul 2, 2026CVE-2026-45058
Electerm: Importing unsafe bookmark data could lead to unsafe operation when clicking local type bookmark
critical9.4No fixMay 14, 2026CVE-2026-45353
Electerm Local code through electerm's single-instance socket
critical7.8May 14, 2026CVE-2026-45787
electerm's encrypt method not safe enough
medium6.0May 14, 2026CVE-2026-43940
Electerm runWidget has a path traversal that leads to arbitrary code execution
critical9.8May 8, 2026
