Skip to main content
Menu
CVEs

MongoDB Java Driver host redirection in SRV seedlist parsing

CVE-2026-129932Published November 19, 2026, updated

9.1CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 5.13.0
Who is exposed
Not reported

Summary

The MongoDB Java Driver checks a DNS seedlist record against the seed domain, but a later parsing step reads the same value differently, so the host that is checked and the host that is used can differ. Remotely and without logging in, an attacker who can set or forge the DNS service record for a connection string's seed domain can redirect the driver to an unrelated host they control, where it may send application data and database credentials and accept certificate verification from that host.

Written by a model

Original 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.

What to do

Upgrade to a fixed version: 5.13.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129932 (Attacker able to redirect a Java driver client to a host they own, surviving TLS certificate verification, via an SRV parent-domain bypass), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129932 (entry last updated 2026-11-19):
Affected:
- MongoDB Java Driver: from 3.6.0, fixed in 5.13.0
Fixed versions: 5.13.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129932 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129932 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://jira.mongodb.org/browse/JAVA-6347
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129932
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129932"}.

Affected versions

cve.now Index

27Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.1, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated1 day
  5. Posted on X by cve.now

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkjira.mongodb.org · browse/JAVA-6347
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129932
RecordNVD · CVE-2026-129932

Questions about CVE-2026-129932

Is CVE-2026-129932 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-129932?

Java Driver: from 3.6.0 before 5.13.0.

Source: cve.now feed data

How do I fix CVE-2026-129932?

Upgrade to a fixed version: 5.13.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.