CVE-2026-88033

8.3

MongoDB · Java Driver

The MongoDB Java Driver GridFS component improperly handles file identifiers, allowing authenticated users to manipulate query logic to access, delete, or rename unintended files.

Executive summary

An authenticated user can exploit improper query neutralization in the MongoDB Java Driver to perform unauthorized file operations, posing a high risk to data integrity and availability.

Vulnerability

This vulnerability, classified as CWE-943, involves the improper neutralization of special elements in data query logic within the GridFS component. An authenticated user who can influence the structured file identifier may cause the driver to execute unauthorized data operations, including unauthorized data access and the destruction of file chunks.

Business impact

The potential for unauthorized modification or deletion of stored data represents a significant threat to business operations and data integrity. Given the CVSS score of 8.3, the vulnerability is classified as high severity, as it enables attackers to render critical file content unreadable or maliciously alter file structures, potentially leading to widespread service disruption.

Remediation

Immediate Action: Update the MongoDB Java Driver to version 5.11.1 or later to resolve the query logic flaw.

Proactive Monitoring: Review application access logs for unusual patterns involving GridFS operations or unexpected file identifier parameters.

Compensating Controls: Implement strict input validation on all file identifiers passed to the GridFS component and apply the principle of least privilege to restrict user access to sensitive buckets.

Exploitation status

Public Exploit Available: No (exploit_available: false)

Analyst recommendation

Organizations utilizing the MongoDB Java Driver should treat this vulnerability with high priority. Because the flaw allows for the manipulation of critical file data, administrators must verify their current driver version and apply the 5.11.1 patch immediately to prevent potential data destruction or unauthorized access within their MongoDB environments.

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