CVE-2026-114649

Authentication bypass via issuer-and-serial-only certificate equality in shared cluster cache

  • High 7.6

Description

The MongoDB C# Driver compares TLS client certificates by issuer and serial number only when deciding whether two clients can share cached connections. In an application that creates clients from certificates supplied by different users, a user who provides a certificate copying another user's issuer and serial number, without that user's private key, can be given connections authenticated with the other user's certificate. Database operations can then run under the other user's identity, affecting the confidentiality and integrity of data that identity can access.

Key facts

Published
22 Oct 2026
Last changed
2 Nov 2026
Assigned by
mongodb
EPSS
0.2% likely to be exploited in the next 30 days, higher than 9.859% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: poc; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.6CVSS 4.0, Highfrom the CNA (mongodb)CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
  • 6.8CVSS 3.1, Mediumfrom the CNA (mongodb)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
MongoDBC# Driver
  • Default status: unaffected
  • 1.8.0 up to but excluding 3.13.0 (affected)

Timeline

  1. 22 Oct 2026 Published

Weakness

References