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).
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).
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | electerm | <= 3.8.15 | no fix |
References
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N- Weakness (CWE)
CWE-200, CWE-312- Platform
- npm
- Package
electerm- Disclosed
- 08.05.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-37j4-88rp-2f6h - CC BY 4.0
Vulnerability history: electerm
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 13
- First → latest
- 01.2023 07.2026
- Without a fix
- 4
- Exploited in attacks
- 0
Severity breakdown
- Critical 7
- High 4
- Medium 2
Disclosures per year
- 2023: 1
- 2024: 0
- 2025: 0
- 2026: 12
-
Electerm's full process.env exposed to renderer via window.pre.env this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.