Quick answers
- Is CVE-2026-88022 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88022 being exploited in the wild.
- How severe is CVE-2026-88022?
- High severity, with a CVSS score of 7.7, published 10 September 2026.
- Which products and versions are affected?
- MongoDB Laravel MongoDB before 5.11.0.
- Is there a fix for CVE-2026-88022?
- A patch was published on 2026-09-10: Fixed in version 5.11.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88022 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-88022?
- Check whether you run MongoDB Laravel MongoDB 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 a query injection flaw in the query builder's where() method. When the three-argument form where($column, '=', $value) or where($column, 'eq', $value) is called with an array $value, the array is embedded directly into the MongoDB filter without proper escaping, causing MongoDB to interpret it as an operator document rather than a literal value. The same issue affects internal methods find($id) and delete($id) which internally use where('_id', '=', $id). An attacker who can inject an operator-shaped array (e.g., ['$ne' => null]) can bypass field-level lookups or delete arbitrary documents. The fix, released in version 5.11.0, wraps array values in an explicit $eq operator for the three-argument form to force literal comparison. The two-argument form where($column, $array) retains its original behavior for intentional operator document construction.
Affected products
- MongoDB Laravel MongoDB before 5.11.0
Timeline
- 2026-09-10: disclosed
- 2026-09-10: patched: Fixed in version 5.11.0