Laravel MongoDB `whereDoesntHave` misses deny records for numeric string IDs
Impact
Laravel MongoDB versions before 5.12.0 are affected by a type-handling flaw, allowing users with basic privileges to access or modify documents they should not. The flaw occurs in the `whereDoesntHave` method. A user may be served, change, or remove documents that the check was intended to withhold.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
MongoDB · mongodb
Laravel MongoDB
1 range
MongoDB · mongodb
Laravel MongoDB
Compare with this publisher’s ranges. This does not inspect your installation.
affected
3.2.3 → before 5.12.0
semver versions
Other versions: unaffected
Original source 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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-118510View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.