Skip to main content
VulnerabilityPublished

CVE-2026-129934: MongoDB GO Driver · Generation of Error Message Containing Sensitive Information

Affects MongoDB GO DriverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.7 Medium : upgrade to 2.10.1 when convenient.

Data as of 19 Nov 2026, 19:49 UTC

CVSS 4.0 base score
5.7Medium
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.05.7
CNA (mongodb)CVSS 3.14.7
Patch
Available – fixed in 2.10.1
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/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 18 Nov 2026.

What to do

Upgrade MongoDB GO Driver to 2.10.1.

Affected software

ProductAffectedFixed in
GO Drivergo.mongodb.org/mongo-driverAffected
  • >=1.0.0
Fixed in–
GO Drivergo.mongodb.org/mongo-driver/v2Affected
  • >=2.0.0 <2.10.1
Fixed in
  • 2.10.1

AI-suggested

A patch is available and should be applied by upgrading the MongoDB Go driver to version 2.10.1 or later. This update fixes the error message handling to prevent leaking raw secret values. Since this is a client library vulnerability, remediation requires updating the affected software. No additional mitigations are specified by the vendor.

Description

CVE-2026-129934 is a vulnerability in the MongoDB Go driver's connection string parser that causes error messages to include raw, undecoded values of query options when they contain invalid percent encodings. If these options hold sensitive data such as TLS key file passwords or AWS session tokens, the secrets are exposed in plain text within the error messages. This can lead to information disclosure if an attacker has low-privileged read access to the application's error logs or displays. The issue affects versions from 1.0.0 and all 2.x versions prior to 2.10.1. A fix is available in version 2.10.1.

References

Community reviews

Loading reviews…