MongoshApplication · MongoDB
CVE-2025-1691
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 mongosh autocomplete feature, can use the autocompletion feature to input and run obfuscated malicious text. This requires user interaction in the form of the user using ‘tab’ to autocomplete text that is a prefix of the attacker’s prepared autocompletion. This issue affects mongosh versions prior to 2.3.9. The vulnerability is exploitable only when mongosh is connected to a cluster that is partially or fully controlled by an attacker.
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 confidenceA control character injection vulnerability exists in mongosh's autocomplete feature where an attacker who controls the MongoDB cluster can inject malicious/obfuscated text into autocomplete suggestions. When a user presses tab to autocomplete text that matches the attacker's prepared prefix, the injected code executes. This requires user interaction and a compromised or attacker-controlled MongoDB cluster.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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.
-
Check installed mongosh versionRun 'mongosh --version' or 'mongosh --eval "db.version()"' to retrieve the mongosh version numberAffected if The version shown is less than 2.3.9 (for example, 2.3.8, 2.3.0, 1.x.x)
-
Identify MongoDB cluster connection sourceReview your mongosh connection string or configuration to determine which MongoDB cluster you are connecting toAffected if You are connected to or regularly connect to a cluster that is not under your direct administrative control, such as a shared or third-party hosted cluster
-
Assess autocomplete usage contextDetermine if autocomplete (pressing Tab) is used in your mongosh workflow for command completionAffected if Tab completion is actively used and the connected cluster could be compromised or controlled by an attacker
You are affected if your mongosh version is below 2.3.9 and you connect to a MongoDB cluster that could be controlled by an attacker who could inject malicious autocomplete suggestions.
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 patch the vulnerability. Since the attacker must control the cluster for exploitation, ensure cluster security and restrict unauthorized access.
2.3.9
- Check current mongosh version by running: mongosh --version
- Download and install mongosh version 2.3.9 or later from the official MongoDB Download Center (https://www.mongodb.com/try/download/shell) or via your system's package manager
- Verify the upgrade was successful by running: mongosh --version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Mongosh
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1691 — 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-1691 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