Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-88029 high CVSS 8.3

Vulnerability in pymongo (CVE-2026-88029)

Summary

Vulnerability in pymongo (CVE-2026-88029). Data can be tampered with by attackers. Mitigation: upgrade to 4.18.1 or later.

Original description

The description as published by the source.

Impact

When reading/writing via an ID with the GridFS API, require an exact match on the given ID. Otherwise, if a Hash is given in place of the ID, it may be interpreted as criteria, overriding the ID match.

Patches

Patch available in pymongo >= 4.18.1

Workarounds

Ensure your existing workflow only supports exact matching on the GridFS API.

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-88029 has been found in pymongo.
Data can be tampered with by attackers. CVSS score: 8.3/10.
What to do: upgrade pymongo to 4.18.1 or later.
If unsure, ask your IT team or search "pymongo CVE-2026-88029" on the vendor's site.

CVE-2026-88029 (pymongo) — CWE-943 / CVSS v3 8.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.18.1 — apply immediately
Workaround: Ensure your existing workflow only supports exact matching on the GridFS API.
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.

❓ What is the problem

A vulnerability (CWE-943) exists in pymongo.

📍 Affected scope

Check the vendor advisory for the affected versions of pymongo.

🔥 Severity

Severity: High (CVSS 8.3/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 4.18.1.

🛡️ Workaround

Workaround: Ensure your existing workflow only supports exact matching on the GridFS API.

🔍 Detection

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

  1. 1
    Identify exposure identify 
    grep -r 'pymongo' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で pymongo を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Ensure your existing workflow _only_ supports exact matching on the GridFS API.

    パッチが適用されるまでの応急処置として、Ensure your existing workflow only supports exact matching on the GridFS API. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade pymongo to 4.18.1

    ステージング環境で 4.18.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip pymongo
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.18.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details