CVE-2026-88033
- Published10 Sept 2026
Description
Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB Java 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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:HAffected products
Remediation
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-88033 being actively exploited?
CVE-2026-88033 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.26%.
How severe is CVE-2026-88033?
CVE-2026-88033 has a CVSS 3.1 base score of 8.3, rated high. EPSS estimates a 0.26% probability of exploitation.
Which products are affected by CVE-2026-88033?
Affected products include Mongodb Java Driver.
How do I fix CVE-2026-88033?
Upgrade affected software to a fixed version, for example Mongodb Java Driver 5.11.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-88033 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.