Is CVE-2026-88023 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-88023 being exploited in the wild.

How severe is CVE-2026-88023?

High severity, with a CVSS score of 8.3, published 10 September 2026.

Which products and versions are affected?

MongoDB PHP Library before 2.4.2 and 1.21.5; mongodb/mongodb (Packagist) ECOSYSTEM:introduced=1.1.0,fixed=1.24.5.

Is there a fix for CVE-2026-88023?

Yes. mongodb/mongodb (Packagist): upgrade to 1.24.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-88023 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-88023?

Check whether you run MongoDB PHP Library or mongodb/mongodb (Packagist) 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.

CVE-2026-88023: MongoDB PHP Library improper query neutralization in GridFS

CVE-2026-88023 · Severity: high · CVSS 8.3 · Published 2026-09-10

The MongoDB PHP Library's GridFS component, used for storing and retrieving large files, fails to properly sanitize file identifiers when building database queries. An authenticated attacker who can control how a file is referenced could read unintended files, delete all files in a storage bucket, or rename the wrong file. This puts sensitive file content at risk of unauthorized access or loss.

Technologies: MongoDB PHP Library, mongodb/mongodb (Packagist). Vendors: MongoDB, Packagist.

Quick answers

Is CVE-2026-88023 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-88023 being exploited in the wild.
How severe is CVE-2026-88023?: High severity, with a CVSS score of 8.3, published 10 September 2026.
Which products and versions are affected?: MongoDB PHP Library before 2.4.2 and 1.21.5; mongodb/mongodb (Packagist) ECOSYSTEM:introduced=1.1.0,fixed=1.24.5.
Is there a fix for CVE-2026-88023?: Yes. mongodb/mongodb (Packagist): upgrade to 1.24.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-88023 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-88023?: Check whether you run MongoDB PHP Library or mongodb/mongodb (Packagist) 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.

How to fix

mongodb/mongodb (Packagist): upgrade to 1.24.5 or later
```
composer require mongodb/mongodb:^1.24.5
```

Technical details

The vulnerability is an improper neutralization of special elements in data query logic (CWE-89 equivalent – query injection) within the GridFS component of the MongoDB PHP Library. The root cause is that caller-supplied file identifiers are interpolated directly into database query conditions instead of being matched as literal values using the $eq operator. An authenticated user with the ability to influence the file identifier parameter can craft a structured object that is interpreted as a query condition, allowing them to retrieve stored file content beyond the intended target, delete all chunks in the affected bucket, or rename unintended files. Attack requires application-level authentication and the ability to control the file ID parameter. Patches are available in version 2.4.2 and 1.21.5.

Affected products

MongoDB PHP Library before 2.4.2 and 1.21.5

Identifiers

CVE-2026-88023
GHSA-8fxw-fmj8-xp7j

Timeline

2026-09-10: disclosed
2026-09-10: patched: Versions 2.4.2 and 1.21.5 released with fix

References

https://jira.mongodb.org/browse/PHPLIB-1929

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.