Quick answers
- Is CVE-2026-88036 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88036 being exploited in the wild.
- How severe is CVE-2026-88036?
- High severity, with a CVSS score of 8.3, published 10 September 2026.
- Which products and versions are affected?
- MongoDB C Driver before 1.30.10 and before 2.5.3.
- Is there a fix for CVE-2026-88036?
- A patch was published on 2026-09-10: Patches released in versions 1.30.10 and 2.5.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88036 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-88036?
- Check whether you run MongoDB C Driver at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an improper neutralization of special elements in query logic (CWE-89 equivalent) within the GridFS component of the MongoDB C Driver. When user-supplied file identifiers are passed to database commands, they are not properly escaped or wrapped with exact-match operators (such as $eq), allowing them to be interpreted as query conditions rather than literal values. An authenticated attacker who can influence file identifiers used by an affected application may retrieve files beyond the intended target or execute delete operations on all GridFS chunks in a bucket. Patches are available in versions 1.30.10 and 2.5.3.
Affected products
- MongoDB C Driver before 1.30.10 and before 2.5.3
Timeline
- 2026-09-10: disclosed: CVE-2026-88036 published
- 2026-09-10: patched: Patches released in versions 1.30.10 and 2.5.3