Quick answers
- Is CVE-2026-96747 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96747 being exploited in the wild.
- How severe is CVE-2026-96747?
- Medium severity, with a CVSS score of 5, published 24 September 2026.
- Which products and versions are affected?
- MongoDB Python Driver before 4.18.2; pymongo (PyPI) >= 3.9.0, <= 4.18.1, ECOSYSTEM:introduced=3.9.0,fixed=4.18.2.
- Is there a fix for CVE-2026-96747?
- Yes. pymongo (PyPI): upgrade to 4.18.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-96747 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-96747?
- Check whether you run MongoDB Python Driver or pymongo (PyPI) 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
- pymongo (PyPI): upgrade to 4.18.2 or later
pip install "pymongo>=4.18.2"
Technical details
The vulnerability stems from improper endpoint URL validation in the key management code path. When a key management endpoint URL ends with ".sock", the driver mistakenly treats it as a local Unix domain socket path rather than a remote hostname. An attacker with database write permissions can modify encrypted field metadata to inject malicious endpoint URLs, causing the application to establish connections to arbitrary local sockets. Data exposure is limited to TLS handshake content only.
Affected products
- MongoDB Python Driver before 4.18.2
Identifiers
- CVE-2026-96747
- GHSA-qx36-8mw2-4r3x
- PYSEC-2026-4295
Timeline
- 2026-09-24: disclosed: CVE-2026-96747 published
- 2026-09-24: patched: Fix released in PyMongo 4.18.2