{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-88022 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-88022 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-88022 is a high-severity SQL injection vulnerability in Laravel MongoDB (PHP), published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-88022 and fix it if it is affected.\n\nWhat it is: CVE-2026-88022 is a high-severity SQL injection vulnerability in Laravel MongoDB (PHP), published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-88022 in the wild and no public exploit code.\n\nAffected product: Laravel MongoDB (PHP). No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-88022/ (Markdown: https://insights.sbomify.com/CVE-2026-88022/index.md)","id":"CVE-2026-88022","markdown":"https://insights.sbomify.com/CVE-2026-88022/index.md","name":"CVE-2026-88022","record":{"aliases":["GHSA-jcw9-p6mm-h9pj"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Laravel MongoDB integration","requires_auth":"none","summary":"Attackers can inject query operators to read or delete unintended documents in Laravel applications using the MongoDB integration.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mongodb","cpe":[{"product":"laravel_mongodb","vendor":"mongodb"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-943","name":"Improper Neutralization of Special Elements in Data Query Logic"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SQL injection in Laravel MongoDB (PHP)","id":"CVE-2026-88022","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"GridFS data disclosure and deletion via query-operator injection in file IDs in the MongoDB PHP Library","id":"CVE-2026-88023"},"packages":[],"prev":{"headline":"Consul vulnerable to an authorization bypass in the Connect service mesh","id":"CVE-2026-88021"},"products":["Laravel MongoDB (PHP)"],"published":"2026-09-10","related":[{"cvss_score":7.1,"headline":"Other in Laravel MongoDB (PHP)","id":"CVE-2026-88027","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":7.1,"headline":"SQL injection in Laravel MongoDB (PHP)","id":"CVE-2026-88028","kev_date_added":null,"published":"2026-09-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-10","vendors":["MongoDB"]},"summary":"Attackers can inject query operators to read or delete unintended documents in Laravel applications using the MongoDB integration.","url":"https://insights.sbomify.com/CVE-2026-88022/"}