Quick answers
- Is CVE-2026-116641 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116641 being exploited in the wild.
- How severe is CVE-2026-116641?
- Medium severity, with a CVSS score of 6.8, published 28 October 2026.
- Which products and versions are affected?
- MongoDB Database Tools 100.19.0 and earlier.
- Is there a fix for CVE-2026-116641?
- Yes: fixed in DB Tools 100.20.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116641 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-116641?
- Check whether you run MongoDB Database Tools 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: DB Tools 100.20.0
Technical details
The vulnerability stems from DB Tools version 100.19.0 being compiled with Golang 1.26.8, which does not include the eMudhra CA certificates in its crypto/x509 denylist. Golang 1.27.3 added these known-bad certificates to prevent their misuse in TLS validation. An attacker with access to a compromised eMudhra CA certificate could conduct man-in-the-middle attacks on TLS connections made by affected DB Tools versions, bypassing certificate validation. The fix requires updating to DB Tools 100.20.0, which uses Golang 1.27.3.
Affected products
- MongoDB Database Tools 100.19.0 and earlier
Timeline
- 2026-10-28: disclosed