CVE-2026-88029

8.3

MongoDB · Python Driver

An improper neutralization of special elements in the MongoDB Python Driver GridFS component allows authenticated users to manipulate data queries, leading to unauthorized file access or data deletion.

Executive summary

The MongoDB Python Driver contains a high-severity vulnerability in its GridFS component that allows an authenticated user to perform unauthorized file operations or data destruction.

Vulnerability

This vulnerability (CWE-943) involves improper neutralization of special elements in data query logic, where a structured file identifier is misinterpreted as a query condition. An authenticated user can leverage this flaw to access unauthorized file content, delete file chunks, or incorrectly rename stored files.

Business impact

The potential for unauthorized data access and the destruction of stored file content poses a significant risk to data integrity and availability. With a CVSS score of 8.3, the vulnerability is classified as high severity, as it allows attackers to render critical file stores unreadable or manipulate sensitive data, which could lead to substantial operational disruption.

Remediation

Immediate Action: Upgrade the MongoDB Python Driver to version 4.18.1 or later to resolve the query logic flaw.

Proactive Monitoring: Review application logs for unusual GridFS rename or deletion operations and monitor database performance for unexpected query patterns.

Compensating Controls: Ensure that application-level input validation is strictly enforced for all identifiers passed to the GridFS component to prevent malicious query injection.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Given the potential for data loss and unauthorized access within the GridFS component, organizations should prioritize updating the MongoDB Python Driver to version 4.18.1. Failure to patch allows authenticated users to bypass intended access controls, potentially resulting in severe data integrity issues across affected buckets.

More MongoDB CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources