laravel mongodb vulnerabilities and fixes
Recent CVEs affecting laravel mongodb, with upgrade or downgrade steps. 3 tracked.
Also searched as: laravelmongodb.
laravel mongodb has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2026-09-10. Highest priority: CVE-2026-88022 (score 41/100).
- CVE-2026-88022 HIGH 7.7 UPGRADE Improper neutralization of special elements in data query logic in the MongoDB integration for Laravel can cau
- CVE-2026-88027 HIGH 7.1 UPGRADE Improper neutralization of special elements in data query logic in the embedded-document relation handling of
- CVE-2026-88028 MEDIUM 6.5 UPGRADE Improper neutralization of special elements in data query logic in the polymorphic relation handling of the Mo
FAQ
How do I fix laravel mongodb vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is laravel mongodb being exploited right now?
None of the tracked laravel mongodb CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which laravel mongodb CVE should I patch first?
CVE-2026-88022 currently ranks highest (41/100): Improper neutralization of special elements in data query logic in the MongoDB integration for Laravel can cau.