Server-side Request Forgery (SSRF) Affecting pymongo package, versions [3.9.0,4.18.2)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-PYTHON-PYMONGO-20158824
- published27 Sept 2026
- disclosed24 Sept 2026
- creditUnknown
Introduced: 24 Sep 2026
NewCVE-2026-96747 (opens in a new tab)How to fix?
Upgrade pymongo to version 4.18.2 or higher.
Overview
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in _EncryptionIO.kms_request and _EncryptionIO.fetch_keys, which pass the endpoint through parse_host() and on to _create_connection unchanged when it ends in .sock, so the connection code interprets it as a Unix domain socket path and connects over AF_UNIX rather than to a network host. A user with write access to the key vault collection can make the application open a connection to a filesystem path of their choosing from inside its own process, by setting masterKey.endpoint on a data key to a value with that suffix. This requires the application to use client side field level encryption or Queryable Encryption against a key vault the attacker can write to, and TLS verification on the KMS connection causes the attempt to fail, which confines the effect to the connection itself.
Note: This is only exploitable if an attacker has write access to the key vault collection used by the application.
Workaround
This vulnerability can be avoided by restricting key vault write access to trusted principals and auditing existing key vault documents for .sock suffixed endpoint values.