# CVE-2026-118510: Laravel MongoDB `whereDoesntHave` misses deny records for numeric string IDs


- **Severity:** High 7.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026

## What is CVE-2026-118510?

CVE-2026-118510 is a high-severity vulnerability in Laravel MongoDB, published on 28 Oct 2026. 

### Official 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.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2026-118510?


## How do I fix CVE-2026-118510?

No fix has been published for CVE-2026-118510 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-118510 being exploited?

There is no known exploitation of CVE-2026-118510 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-118510 and fix it if it is affected.

What it is: CVE-2026-118510 is a high-severity vulnerability in Laravel MongoDB, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118510 in the wild and no public exploit code.

Affected product: Laravel MongoDB. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-118510/ (Markdown: https://insights.sbomify.com/CVE-2026-118510/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-118510
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-118510
- OSV: https://osv.dev/vulnerability/CVE-2026-118510

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-118510/
Summaries are generated and may contain mistakes; the official description above is the record.