CVE-2026-118510

Laravel MongoDB `whereDoesntHave` misses deny records for numeric string IDs

Published Oct 28, 2026 CVSS 4.0 · 7.7 High EPSS < 1% KEV · Not listed
Description
A type-handling flaw in the relationship query building of this MongoDB integration library can cause a check for the absence of a related record to be compiled with an identifier of the wrong data type. In an application that relies on such a check to decide which documents a request may see or act on, a user with basic privileges may be served, may change, or may remove documents that the check was intended to withhold. The failure is silent and produces no error.

Analysis

AI-generated

Technical impact

The vulnerability is a type handling flaw in the whereDoesntHave query method of the Laravel MongoDB integration library. Because numeric string identifiers are incorrectly cast, the resulting query incorrectly allows records that should be excluded. A user with ordinary privileges can therefore view, modify, or delete documents that the access control logic was intended to protect. This can lead to confidentiality, integrity, and availability breaches of application data.

Affected Systems

All versions of the MongoDB integration library for Laravel, prior to the 5.12.0 release, are affected. The issue is present in applications that use the whereDoesntHave method to enforce record visibility constraints. The library is distributed under the name MongoDB:Laravel MongoDB.

Risk and Exploitability

The CVSS score of 7.7 indicates a high severity. The EPSS score is not available, but the bug can be exploited silently without error output, making detection difficult. Since it is not listed in CISA KEV, there is no confirmed exploitation yet, but the vulnerability is suitable for privilege escalation attacks that require no privileged access. The most likely attack path is via a web application endpoint that uses whereDoesntHave; a basic authenticated user can supply numeric string IDs to bypass the restriction.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Laravel MongoDB integration library to version 5.12.0 or later.
  • Verify that the application does not rely solely on whereDoesntHave for enforcing access controls and apply additional checks if necessary.
  • Conduct a code review of all relations that use whereDoesntHave to ensure proper type handling and consider refactoring the query logic if updates are delayed.

Generated by OpenCVE AI on October 28, 2026 at 17:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Mongodb
Mongodb laravel Mongodb
Vendors & Products Mongodb
Mongodb laravel Mongodb
Type Values Removed Values Added
Description A type-handling flaw in the relationship query building of this MongoDB integration library can cause a check for the absence of a related record to be compiled with an identifier of the wrong data type. In an application that relies on such a check to decide which documents a request may see or act on, a user with basic privileges may be served, may change, or may remove documents that the check was intended to withhold. The failure is silent and produces no error.
Title Laravel MongoDB `whereDoesntHave` misses deny records for numeric string IDs
Weaknesses CWE-843
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 7.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-843

    Access of Resource Using Incompatible Type ('Type Confusion')

Sources

Status
PUBLISHED
Assigner
mongodb
Published
Updated
Nov 5, 2026, 6:57 PM
Reserved
Oct 28, 2026, 1:54 PM
Status
Awaiting Analysis
Published
Oct 28, 2026, 5:18 PM
Modified
Nov 5, 2026, 7:17 PM