MongoshApplication · MongoDB
CVE-2025-1692
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe MongoDB Shell may be susceptible to control character injection where an attacker with control of the user’s clipboard could manipulate them to paste text into mongosh that evaluates arbitrary code. Control characters in the pasted text can be used to obfuscate malicious code. This issue affects mongosh versions prior to 2.3.9
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe MongoDB Shell (mongosh) is vulnerable to control character injection where an attacker who controls the user's clipboard can inject malicious text containing control characters. When the victim pastes this text into mongosh, the control characters can obfuscate the malicious code, causing it to be evaluated as arbitrary code rather than being visible as such.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
MongoshApplication
< 2.3.9CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify mongosh is installedRun 'mongosh --version' or 'mongosh -v' in your terminal to see if mongosh is available and retrieve its version numberAffected if mongosh is installed and the version is below 2.3.9
-
Check alternative version commandIf the above fails, try 'which mongosh' to locate the executable, then run the version flag from the installed pathAffected if The installed mongosh binary reports a version lower than 2.3.9
-
Compare version against affected rangeCompare the reported version number to the affected range: any version < 2.3.9 is vulnerable. Note that this vulnerability requires the victim to paste clipboard content into mongoshAffected if Your installed version is 2.3.8 or lower
You are affected if mongosh is installed and its version is lower than 2.3.9, and users paste clipboard content into the mongosh shell.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.3.9
Upgrade mongosh to version 2.3.9 or later to receive the patch for this vulnerability.
mongosh 2.3.9
- Check current mongosh version by running: mongosh --version
- Upgrade mongosh to version 2.3.9 or later using your package manager (e.g., npm install -g mongodb-mongosh@latest, brew upgrade mongosh, or apt-get upgrade mongodb-mongosh)
- Verify the upgrade was successful by running: mongosh --version and confirming the version is 2.3.9 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Mongosh
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1692 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-1692 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data