dbcve.org
MongoDBDatabase / datastore

CVE-2026-9742

MEDIUM · 5.9 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 8.2.10 / 8.3.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click Patch available

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 · unedited
When OIDC authentication is enabled in configuration, clients may set specific values in the "mechanism" parameter of the "authenticate" command that lead to server crash. The authenticate command is accessible to unauthenticated clients, leading to pre-auth denial-of-service in affected product configurations.

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

A detailed technical summary for this CVE is being prepared.

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
MongoDBDatabase / datastore
Affected:>= 8.2.0, < 8.2.10>= 8.3.0, < 8.3.3

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

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 · scoped
Upgrade available Upgrade to 8.2.10 / 8.3.3 or later
Fixed in 8.2.108.3.3
Vendor patch jira.mongodb.org →
Recommended fix High confidence

8.2.10 for 8.2.x branches; 8.3.3 for 8.3.x branches

  1. 1. Identify current MongoDB version using: db.version() or mongod --version
  2. 2. Determine target upgrade version based on current branch: if on 8.2.x upgrade to 8.2.10, if on 8.3.x upgrade to 8.3.3
  3. 3. Create backup of all databases and configuration files before upgrading
  4. 4. Stop MongoDB service: systemctl stop mongod or service mongod stop
  5. 5. Upgrade MongoDB packages using package manager (e.g., apt-get upgrade mongodb-org, yum update mongodb-org, or dpkg -i for direct package)
  6. 6. Verify configuration files are compatible with new version
  7. 7. Start MongoDB service: systemctl start mongod or service mongod start
  8. 8. Confirm server is running and accessible: mongosh -e 'db.adminCommand({ping:1})'
Caveat Standard patch upgrade with no expected breaking changes; always review MongoDB release notes for minor version-specific changes

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9742 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9742 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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