Vulnerability in Laravel Mongodb (CVE-2026-88022)
Summary
Vulnerability in Laravel Mongodb (CVE-2026-88022). Data can be tampered with by attackers. Exploitable via where.
Original description
The description as published by the source.
Improper neutralization of special elements in data query logic in the MongoDB integration for Laravel can cause an array supplied to an explicit equality filter to be interpreted as a query condition rather than as a literal value. This affects the three-argument where method when the operator is = or eq, as well as the find and delete methods that use that code path. An attacker who can cause an affected application to supply an operator-shaped array to one of these APIs may obtain a document other than the intended target or delete documents beyond the intended target.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-88022 has been found in Laravel Mongodb.
Attackers can target a specific entry point like where over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Laravel Mongodb CVE-2026-88022" on the vendor's site.
CVE-2026-88022 (Laravel Mongodb) — CWE-943 / CVSS v3 7.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: where / find / delete
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-943) exists in Laravel Mongodb. Attackers reach the vulnerable code path via where without authentication.
Check the vendor advisory for the affected versions of Laravel Mongodb. Attack surface: where / find / delete.
Severity: High (CVSS 7.7/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Laravel Mongodb を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web jira.mongodb.org
- web nvd.nist.gov
- web github.com