What is CVE-2026-88023?

CVE-2026-88023 is a medium-severity security vulnerability in mongodb/mongodb (composer), affecting versions >= 1.1.0, < 1.21.5. It is fixed in 1.24.5, 2.4.2.

Which versions of mongodb/mongodb are affected by CVE-2026-88023?

mongodb/mongodb (composer) versions >= 1.1.0, < 1.21.5 is affected.

Is there a fix for CVE-2026-88023?

Yes. CVE-2026-88023 is fixed in 1.24.5, 2.4.2. Upgrade to this version or later.

Is CVE-2026-88023 exploitable, and should I be worried?

Whether CVE-2026-88023 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-88023 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-88023?

Upgrade: mongodb/mongodb to 1.24.5 or later, mongodb/mongodb to 2.4.2 or later.

CVE-2026-88023 in mongodb/mongodb

Q: Which versions of mongodb/mongodb are affected by CVE-2026-88023?

mongodb/mongodb (composer) versions >= 1.1.0, < 1.21.5 is affected.

Q: Is there a fix for CVE-2026-88023?

Yes. CVE-2026-88023 is fixed in 1.24.5, 2.4.2. Upgrade to this version or later.

Q: Is CVE-2026-88023 exploitable, and should I be worried?

Whether CVE-2026-88023 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-88023 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-88023?

Upgrade: mongodb/mongodb to 1.24.5 or later, mongodb/mongodb to 2.4.2 or later.

Summary

MongoDB: GridFS data disclosure and deletion via query-operator injection in file IDs

Workarounds

Validate GridFS IDs.

References

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

Impact

Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB PHP Library 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.

Affected versions

mongodb/mongodb (>= 1.1.0, < 1.21.5) mongodb/mongodb (>= 2.0.0, < 2.4.2)

Security releases

mongodb/mongodb → 1.24.5 (composer) mongodb/mongodb → 2.4.2 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Fixed in 1.21.5 and 2.4.2.

Frequently Asked Questions

What is CVE-2026-88023? CVE-2026-88023 is a medium-severity security vulnerability in mongodb/mongodb (composer), affecting versions >= 1.1.0, < 1.21.5. It is fixed in 1.24.5, 2.4.2.
Which versions of mongodb/mongodb are affected by CVE-2026-88023? mongodb/mongodb (composer) versions >= 1.1.0, < 1.21.5 is affected.
Is there a fix for CVE-2026-88023? Yes. CVE-2026-88023 is fixed in 1.24.5, 2.4.2. Upgrade to this version or later.
Is CVE-2026-88023 exploitable, and should I be worried? Whether CVE-2026-88023 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-88023 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-88023?
- Upgrade mongodb/mongodb to 1.24.5 or later
- Upgrade mongodb/mongodb to 2.4.2 or later

Other vulnerabilities in mongodb/mongodb

CVE-IDSeverityPackage summary

CVE-2026-81525Highmongodb/mongodb: mongodb: Reject "." and NUL bytes in database and collection names CVE-2021-32050Mediummongodb/mongodb: MongoDB Driver may publish events containing authentication-related data