CVE-2026-88028: Laravel MongoDB (PHP) · Improper Neutralization of Special Elements in Data Query Logic
Affects Laravel MongoDB (PHP)Source CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 5.11.0 soon.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-09-10.
- Patch
- Available – fixed in 5.11.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.
What to do
Upgrade Laravel MongoDB (PHP) to 5.11.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MongoDBLaravel MongoDB (PHP) | Affected
| Fixed in
|
AI-suggested
Upgrade affected installations of Laravel MongoDB integration to version 5.11.0 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated by the vendor advisory. Applying the official fix fully addresses the issue.
Description
CVE-2026-88028 is a high-severity vulnerability in the MongoDB integration for Laravel (PHP) affecting versions from 1.2.0 up to but not including 5.11.0. It involves improper neutralization of special elements in data query logic within polymorphic relation handling. This flaw allows an authenticated user who can influence a stored relation identifier to cause the application to interpret that identifier as a query condition rather than a literal identifier, potentially returning unintended documents. A fix is available in version 5.11.0.