Is CVE-2026-114649 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-114649 being exploited in the wild.

How severe is CVE-2026-114649?

Medium severity, with a CVSS score of 6.8, published 22 October 2026.

Which products and versions are affected?

MongoDB C Driver versions before 3.13.0.

Is there a fix for CVE-2026-114649?

Yes: fixed in 3.13.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-114649 attacked?

It is attacked over the network or with local access, in a software library.

Am I affected by CVE-2026-114649?

Check whether you run MongoDB C Driver at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-114649: MongoDB C# Driver X.509 certificate identity spoofing via issuer-serial comparison

CVE-2026-114649 · Severity: medium · CVSS 6.8 · Published 2026-10-22

The MongoDB C# Driver uses an insecure method to compare client TLS certificates when sharing database connections, checking only the issuer name and serial number instead of the full certificate content. An attacker with knowledge of another user's certificate metadata can create a forged certificate copy and gain authenticated database access under the legitimate user's identity, potentially exposing or modifying sensitive data.

Technologies: MongoDB C Driver. Vendors: MongoDB.

Quick answers

Is CVE-2026-114649 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114649 being exploited in the wild.
How severe is CVE-2026-114649?: Medium severity, with a CVSS score of 6.8, published 22 October 2026.
Which products and versions are affected?: MongoDB C Driver versions before 3.13.0.
Is there a fix for CVE-2026-114649?: Yes: fixed in 3.13.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114649 attacked?: It is attacked over the network or with local access, in a software library.
Am I affected by CVE-2026-114649?: Check whether you run MongoDB C Driver at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 3.13.0

Technical details

The vulnerability exists in SslSettings.Equals (line 279), which compares X.509 certificate collections using .NET's default X509Certificate.Equals, which only compares issuer DN and serial number while ignoring the private key and certificate content. ClusterKey.CalculateHashCode (lines 189-196) further weakens this by only hashing credential and servers, allowing forged certificates to collide in the cluster cache. When two MongoClient instances share matching ClusterKey values, ClusterRegistry reuses the cached cluster and its TLS connections, causing the second client's commands to execute authenticated as the first client's X.509 identity. The attack requires the attacker to control the certificate object supplied to MongoClientSettings, co-reside in the same process, and know the target's server endpoints.

Affected products

MongoDB C# Driver versions before 3.13.0

Timeline

2026-10-22: disclosed: CVE-2026-114649 published
2026-10-22: patched: MongoDB C# Driver 3.13.0 released with fix

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.