Vulnerability in pymongo (CVE-2026-96749)
Summary
Vulnerability in pymongo (CVE-2026-96749). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.18.2 or later.
Original description
The description as published by the source.
An integer overflow in the BSON document encoding component of the MongoDB Python Driver's bundled native extension may occur when a single document is built from an unusually large amount of caller-supplied data. Size arithmetic is performed in a signed 32-bit type, and the guard meant to catch the overflow is written in a form whose behavior is not defined by the C language standard. A party with no privileges who can place a very large value into data that an application encodes may, depending on how the native extension was built, cause a write outside the bounds of an allocated buffer inside the application's own process.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-96749 has been found in pymongo.
Successful exploitation can lead to full system takeover. CVSS score: 8.4/10.
What to do: upgrade pymongo to 4.18.2 or later.
If unsure, ask your IT team or search "pymongo CVE-2026-96749" on the vendor's site.
CVE-2026-96749 (pymongo) — CWE-190 / CVSS v3 8.4
Attack vector: local / unauthenticated / no user interaction
Patched: 4.18.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-190) exists in pymongo.
Check the vendor advisory for the affected versions of pymongo.
Severity: High (CVSS 8.4/10). Successful exploitation can lead to full system takeover.
Update to 4.18.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pymongo' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pymongo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pymongoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pymongo to 4.18.2ステージング環境で 4.18.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web mongodb.com