Quick answers
- Is CVE-2026-118510 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118510 being exploited in the wild.
- How severe is CVE-2026-118510?
- High severity, with a CVSS score of 8.8, published 28 October 2026.
- Which products and versions are affected?
- MongoDB Laravel MongoDB before 5.12.0.
- Is there a fix for CVE-2026-118510?
- Yes: fixed in 5.12.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118510 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118510?
- 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.
How to fix
- Fixed in: 5.12.0
Technical details
A type-handling flaw in relationship query building causes checks for absent related records to use identifiers with incorrect data types, allowing the check to be bypassed. This occurs in HasOneThrough and HasManyThrough relation queries when an application relies on such checks for access control. An attacker with basic privileges can exploit this to access or modify documents the check was intended to withhold, and the failure produces no error, making it silent and difficult to detect.
Affected products
- MongoDB Laravel MongoDB before 5.12.0
Timeline
- 2026-10-28: disclosed
- 2026-10-26: patched