Mongodb Java Driver
CVE-2026-88033
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.
What this means for your business
- It affects Mongodb Java Driver. It matters if your company, or a supplier that handles your data, runs it.
- An attacker can use it remotely, over a network, with an ordinary user login, and without anyone at your company clicking anything.
- FIRST's prediction model gives it a 0.3% chance of attack attempts being seen in the next 30 days, ranking above 17% of all known flaws.
What to do
- 1Check whether your company or your suppliers run Mongodb Java Driver, and which version. The affected versions are listed further down this page.
- 2If you do, apply the vendor's fix. A patch or vendor advisory has been published.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Scoring
- CVSS
- 8.3 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H- CVSS v4
- 6.1
- Weakness
- CWE-943
- Assigned by
- cna@mongodb.com
Dates
- Published
- 2026-09-10
- Last modified
- 2026-09-16
- Sources
- NVD
Affected products
- Mongodb Java Driver3.3.0 - 5.11.1
As listed in the NVD configuration data. Not a statement about your estate.