mongosh vulnerable to local privilege escalationGHSA-f5w3-73h4-jpcm
HIGHGHSA-f5w3-73h4-jpcm is a high-severity (CVSS 7.5) CWE-426 vulnerability in mongosh. A fix is available for mongosh — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-f5w3-73h4-jpcm.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
mongoshnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | mongosh | all versions | 2.3.0npm install mongosh@2.3.0 |
Affected Products
mongoshmongodbcodeready linux builder eusredhatcodeready linux builder for arm64 eusredhatcodeready linux builder for ibm z systems eusredhatcodeready linux builder for power little endian eusredhatenterprise linux eusredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mongosh, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mongosh to 2.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f5w3-73h4-jpcm is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is GHSA-f5w3-73h4-jpcm in your dependencies?
Find it across npm, including transitive dependencies.