Skip to main content
VulnerabilityPublished

CVE-2026-129932: MongoDB Java Driver · Interpretation Conflict

Affects MongoDB Java DriverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 5.13.0 as a priority.

Data as of 19 Nov 2026, 21:34 UTC

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (mongodb)CVSS 4.09.1
CNA (mongodb)CVSS 3.17.4
Patch
Available – fixed in 5.13.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Java Driver and org.mongodb/mongodb-driver to 5.13.0.

Affected software

ProductAffectedFixed in
MongoDBJava DriverAffected
  • >=3.6.0 <5.13.0
Fixed in
  • 5.13.0
Mavenorg.mongodb/mongodb-driverpkg:maven/org.mongodb/mongodb-driverOther threatsAffected
  • >=3.6.0 <5.13.0
Fixed in
  • 5.13.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix for this vulnerability is available in MongoDB Java driver version 5.13.0. Users should upgrade to version 5.13.0 or later to remediate this issue. No other mitigation steps are indicated by the vendor advisory.

Description

The MongoDB Java driver applies its DNS seedlist domain restriction to a record value that is later re-interpreted differently when the connection target is parsed, so the name that is checked and the name that is used can differ. An unauthenticated party who can set or forge the DNS service record for the seed domain in a connection string can cause the driver to direct its session to an unrelated host and to complete certificate verification against that host instead. This may result in unintended disclosure of application data and of configured database credentials, and in unintended content being returned to the application as query results.

References

Community reviews

Loading reviews…