How severe is CVE-2026-88029?

No CVSS score has been assigned to CVE-2026-88029 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-88029?

CVE-2026-88029 affects the following packages: pymongo (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-88029?

Update pymongo to 4.18.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-88029 is resolved across your whole dependency graph.

How do I detect CVE-2026-88029 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pymongo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-88029 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-88029 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-88029 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-88029?

CVE-2026-88029 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 18th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-88029?

CVE-2026-88029 is classified as CWE-943 (CWE-943). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-88029 published, and has it been updated?

CVE-2026-88029 was published on September 10, 2026 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2026-88029: pymongo — Fixed in 4.18.1

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-88029.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk-0.21%

Lower risk than most CVEs18th percentile — riskier than 18% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍pymongo

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB Python Driver can cause a caller-supplied structured file identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence the identifier passed by an affected application may obtain stored file content beyond the intended target or cause all GridFS file chunks in the affected bucket to be removed, rendering stored file content unreadable. The affected rename operation may also rename a stored file other than the intended target.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pymongo`	all versions	4.18.1`pip install --upgrade 'pymongo==4.18.1'`

Affected Products

1 product · 1 configurations

Application

python drivermongodb

≥ 1.6 && < 4.18.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pymongo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pymongo to 4.18.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-88029 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability is rated as Important because an authenticated user who can influence a GridFS file identifier can delete all file chunks in the affected bucket, making stored files unreadable, and can retrieve or rename a file other than the intended target. Exploitation requires an application to pass a…

Workaround published by Red Hat

There is no complete mitigation for applications that must accept untrusted structured GridFS file identifiers. The following measures reduce risk until a patched pymongo is available: 1. Pass only literal identifiers to GridFS download, delete, and rename operations (ObjectId, string, or integer). Do not pass dictionaries, BSON documents, or other structured values derived from user input. 2. Restrict which authenticated users can invoke GridFS operations, and do not expose GridFS APIs to untrusted clients. 3. If GridFS is not required, avoid using the gridfs module.

Source: Red Hat security advisory for CVE-2026-88029 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Enterprise Linux 8	`python36:3.6-8100020261001091315.4c5117ad`	RHSA-2026:82858
Red Hat OpenShift AI 2.25	`rhoai/odh-llama-stack-core-rhel9:1791873747`	RHSA-2026:87410
Red Hat OpenShift AI 3.4	`rhoai/odh-llama-stack-core-rhel9:1790958470`	RHSA-2026:84734
Red Hat OpenShift AI 3.5	`rhoai/odh-ogx-core-rhel9:1790963109`	RHSA-2026:86891

Frequently Asked Questions

Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB Python Driver can cause a caller-supplied structured file identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence the identifier passed by an affected application may obtain stored file content beyond the intended target or cause all GridFS file chunks in the affected bucket to be removed, rendering stored file content unreadable. The affected rename operation may also rename a stored file other than the intended target.

O3 Security · Impact-Aware SCA

Is CVE-2026-88029 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2026-88029 — pymongo