Skip to main content

CVE-2026-129932MongoDB Java Driver interpretation conflict

High priorityCritical9.1EPSS not scored yet

CVE-2026-129932 is a interpretation conflict in MongoDB Java Driver, rated critical (9.1 on CVSS 4.0).

Why this priority: Critical, and reachable over the network without an account.

Published · Updated · NVD status: Received

What it is

Two components read the same input differently, and an attacker exploits the gap.

How it is reached

An attacker can exploit it over the network, without an account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.

What an attacker gains

A successful attack can read the data it protects and change data or behaviour. In practice, this kind of flaw lets an attacker smuggle requests past the proxy's checks.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade MongoDB Java Driver to 5.13.0 or later.
  2. Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.

Description from NVD

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 this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Proxies, load balancers and the servers behind them. The flaw sits between a front-end proxy and its back end.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • Between a front-end proxy and its back end. An attacker who crosses it can smuggle requests past the proxy's checks.

Questions to answer about your own systems

  • Where does MongoDB Java Driver run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.