# CVE-2026-96744: MongoDB laravel-mongodb cache lock injection

Source: https://junglewise.ai/threats/cve-2026-96744-improper-neutralization-of-special-elements-in-data-query-logic  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-24. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-96744 · Severity: high · CVSS 7.1 · Published 2026-09-24

The MongoDB integration for Laravel improperly handles lock owner values in its cache locking mechanism. An authenticated attacker who can control the lock owner parameter can inject MongoDB aggregation expressions, allowing them to bypass lock ownership checks, take over locks held by other processes, or prematurely expire them. This can lead to race conditions, data corruption, or duplicate operations in applications relying on distributed locks.

Technologies: [MongoDB Laravel MongoDB](https://junglewise.ai/threats/technologies/laravel-mongodb). Vendors: [MongoDB](https://junglewise.ai/threats/vendors/mongodb).

## Quick answers

**Is CVE-2026-96744 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-96744 being exploited in the wild.

**How severe is CVE-2026-96744?** High severity, with a CVSS score of 7.1, published 24 September 2026.

**Which products and versions are affected?** MongoDB Laravel MongoDB before 5.11.0.

**Is there a fix for CVE-2026-96744?** 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-96744 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-96744?** 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 exists in MongoLock::acquire() where the lock owner string is embedded directly in MongoDB aggregation pipeline expressions ($eq and $cond) without proper literal wrapping. When an attacker supplies an owner value starting with a dollar sign, MongoDB interprets it as a field-path expression rather than a literal string, bypassing ownership and expiry checks. The fix wraps the owner value in $literal expressions to ensure it is always treated as a literal string during aggregation pipeline evaluation.

## Affected products

- MongoDB laravel-mongodb before 5.11.0

## Timeline

- 2026-09-24: disclosed
- 2026-09-10: patched: Fixed in version 5.11.0

## References

- [https://github.com/mongodb/laravel-mongodb/pull/3579](https://github.com/mongodb/laravel-mongodb/pull/3579)
- [https://github.com/mongodb/laravel-mongodb/releases/tag/5.11.0](https://github.com/mongodb/laravel-mongodb/releases/tag/5.11.0)

## Related threats

- [MongoDB Laravel integration library type-handling flaw in relation queries](https://junglewise.ai/threats/cve-2026-118510-a-type-handling-flaw-in-the-relationship-query-building-of-this)
- [MongoDB Integration for Laravel query injection in where method](https://junglewise.ai/threats/cve-2026-88022-mongodb-integration-for-laravel-query-injection-in-where-method)