Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/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:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-45353 is a critical-severity Code Injection (CWE-94) vulnerability in Electerm Project Electerm. Its CVSS base score is 9.3 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Executable Installer File Permissions Weakness (T1574.005); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-17 (Remote Access) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-32960
Vulnerability Data
electerm is an open-sourced terminal/ssh/sftp/telnet/serialport/RDP/VNC/Spice/ftp client. From 3.0.6 to 3.8.8, This vulnerability is fixed in 3.9.0.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 5 hardening rules · 3 OS baselines
V1.3.1V3.5.3V10.6.2V15.2.4
Mitigating Controls (NIST 800-53 r5) AI
Enforces the access control policy that defines permissions on resources, thereby stopping incorrect assignments from remaining exploitable.
IA-3 requires unique identification and authentication of devices before any communication channel is established, directly stopping acceptance of unverified origins.
AC-17 mandates documented restrictions and authentication requirements for remote access, blocking channels whose origins are not properly verified.
Directly requires assignment of only the minimum necessary permissions, preventing overly broad grants on critical resources.
Developer testing and evaluation finds code paths that accept and execute externally influenced strings.
Input validation directly stops untrusted data from being used to construct executable code without neutralization.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.PS-06's SDLC practices directly target injection flaws via secure coding and testing (mostly), yet as a single broad outcome it leaves many code-generation specifics unaddressed (partial).
Authentication of users/services/hardware directly enforces source verification for communication channels.
Verifying identity assertions prevents spoofed channel origins but does not cover all channel-establishment scenarios.
Directly requires defining, enforcing, and reviewing access permissions and least privilege on resources.
Network protections reduce unauthorized channel usage but do not specifically require origin verification at channel setup.
Hardened baselines and configuration management explicitly include correct permission settings for critical resources.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Topic-specific policies on asset management and secure configuration establish expectations for correct permission settings on critical resources, lowering the likelihood that default or overly permissive permissions will be left in place.
Classification results drive the assignment of permissions and handling procedures, decreasing the likelihood that critical resources receive incorrect or overly permissive permission settings.
By requiring owners to determine and document the exact permissions needed for each asset, the control reduces the likelihood that default or overly permissive file and resource permissions will be left in place.
Documented provisioning and revocation procedures reduce the chance that critical resources retain overly permissive default or leftover permissions after personnel changes.
Documented responsibility for protecting assets encourages correct permission settings rather than leaving them at insecure defaults.
Monitoring supplier policy changes and conducting audits can reveal incorrect permission assignments on resources managed by the supplier, prompting corrective action before they are exploited.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248577 OL 8 must enable kernel parameters to enforce Discretionary Access Control (DAC) on symlinks. prevents CWE-732
Windows Server 2016 (2 rules)
- V-224972 Active Directory Group Policy objects must have proper access control permissions. prevents CWE-732
- V-224831 Local volumes must use a format that supports NTFS attributes. prevents CWE-732
Windows Server 2019 (2 rules)
- V-205741 Windows Server 2019 Active Directory Group Policy objects must have proper access control permissions. prevents CWE-732
- V-205663 Windows Server 2019 local volumes must use a format that supports NTFS attributes. prevents CWE-732