Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:HSummary
CVE-2025-1756 is a high-severity Untrusted Search Path (CWE-426) vulnerability in Mongodb Mongosh. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 4th 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 CM-6 (Configuration Settings) and CM-7 (Least Functionality) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-1756 is a local privilege escalation vulnerability in mongosh, affecting versions prior to 2.3.0. The flaw occurs under certain conditions when a crafted file is stored in C:\node_modules\, potentially enabling unauthorized actions on a user's system with elevated privileges. It is linked to CWE-426 (Untrusted Search Path) and carries a CVSS v3.1 base score of 7.5 (AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H), indicating high severity with local access required, high complexity, low privileges, and user interaction.
A local attacker with low privileges can exploit this vulnerability by placing a crafted file in the C:\node_modules\ directory. Exploitation demands high attack complexity and relies on user interaction, likely involving the execution of mongosh in an environment that loads the malicious file via an untrusted search path. Upon success, the attacker achieves privilege escalation, resulting in high impacts to confidentiality, integrity, and availability across the system's scope.
MongoDB's advisory at https://jira.mongodb.org/browse/MONGOSH-2028 and Red Hat's errata at https://access.redhat.com/errata/RHSA-2025:1756 detail the issue. Mitigation requires upgrading to mongosh 2.3.0 or later, which addresses the vulnerability.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-5459
Vulnerability Data
mongosh may be susceptible to local privilege escalation under certain conditions potentially enabling unauthorized actions on a user's system with elevated privilege, when a crafted file is stored in C:\node_modules\. This issue affects mongosh prior to 2.3.0
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Secure baseline settings can enforce absolute, organization-controlled paths for critical resources.
Least-functionality configuration can prohibit unapproved directories or executables from being reachable via search paths.
Engineering principles such as trusted paths, complete mediation, and least privilege directly require hard-coded or validated search paths instead of external ones.
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.
Preventing execution of unauthorized code directly blocks the malicious binaries that an untrusted search path would load.
Secure development practices include avoiding or sanitizing externally influenced search paths in application code.
Hardened configuration baselines can enforce safe search paths and restrict environment variables that enable the weakness.
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.
Security testing can discover search-path issues but does not itself prevent them in production code.
Restricting software installation reduces the chance that untrusted binaries or libraries are placed in search paths.
Secure architecture principles include hard-coded or validated search paths and avoiding reliance on untrusted directories.
Secure coding standards require absolute paths or integrity-checked search paths, directly mitigating CWE-426.
Change-management processes can enforce review of path-handling changes, indirectly lowering risk.