Security Resilience

CVE-2023-39726

Mintty Project Mintty ≤ 3.6.4

Published
26 October 2023
Modified
21 November 2024
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.012 68th percentile
Risk Priority 74 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-39726 is a critical-severity Static Code Injection (CWE-96) vulnerability in Mintty Project Mintty. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique NTDS (T1003.003); ranked in the top 32% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

An issue in Mintty v.3.6.4 and before allows a remote attacker to execute arbitrary code via crafted commands to the terminal.

CWE(s)
NVD-CWE-noinfoCWE-96

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003.003 NTDS Credential Access
Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights.
attack.mitre.org →
T1003.004 LSA Secrets Credential Access
Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.
attack.mitre.org →
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
attack.mitre.org →
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
attack.mitre.org →
T1010 Application Window Discovery Discovery
Adversaries may attempt to get a listing of open application windows.
attack.mitre.org →
T1016.001 Internet Connection Discovery Discovery
Adversaries may check for Internet connectivity on compromised systems.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-1052Same product: Mintty Project Mintty
CVE-2024-0788Shared CWE-96
CVE-2025-36595Shared CWE-96
CVE-2024-13268Shared CWE-96
CVE-2024-13264Shared CWE-96
CVE-2026-68489Shared CWE-96
CVE-2025-30091Shared CWE-96
CVE-2024-13265Shared CWE-96
CVE-2025-57707Shared CWE-96
CVE-2024-32487Shared CWE-96

Affected Assets

mintty project
mintty
≤ 3.6.4

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SC-34 Non-modifiable Executable Programs
addresses: CWE-96

Eliminates the possibility of static code injection into saved executables by making the storage non-modifiable.

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 partial match
blocks

Secure SDLC practices directly require input neutralization to block static code injection into templates, configs, or libraries.

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.

A.8.19 Installation of software on operational systems partial match
removes
A.8.25 Secure development life cycle partial match
blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reach static code injection when applied to the relevant development activities, but leaves a bounded remainder where implementation is incomplete or the flaw slips through the process (as with any SDLC control).

A.8.26 Application security requirements partial match
blocks

A.8.26 requires identifying and specifying requirements (incl. resilience against SQL injections, input validation, and output controls) that would address static code injection if implemented, but the control itself only mandates the requirements process and does not enforce or implement the neutralizing mechanisms.

A.8.27 Secure system architecture and engineering principles partial match
blocks

A.8.27 mandates security-by-design principles (e.g. input sanitization, distrust external input, secure defaults) and design reviews that can stop static code injection from being introduced, but this is only one minority slice of CWE-96 (which also arises in runtime template engines, config parsers, and library generation outside the initial architecture review).

A.8.28 Secure coding partial match
prevents

Secure coding explicitly requires proper neutralization of directives in templates, libraries and configuration files.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing in development and acceptance will detect static code injection but does not prevent it at the source.

References