{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-93759 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-93759 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-93759 is a high-severity code injection vulnerability in MongoDB Inc. Mongoid, published on 18 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-93759 and fix it if it is affected.\n\nWhat it is: CVE-2026-93759 is a high-severity code injection vulnerability in MongoDB Inc. Mongoid, published on 18 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-93759 in the wild and no public exploit code.\n\nAffected product: MongoDB Inc. Mongoid. 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-93759/ (Markdown: https://insights.sbomify.com/CVE-2026-93759/index.md)","id":"CVE-2026-93759","markdown":"https://insights.sbomify.com/CVE-2026-93759/index.md","name":"CVE-2026-93759","record":{"aliases":["GHSA-vr6j-ghpr-hmgf"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"MongoDB Ruby driver","requires_auth":"none","summary":"Attackers can inject server-side JavaScript into Mongoid queries, leading to data disclosure and potential code execution on the database.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mongodb","cpe":[{"product":"mongoid","vendor":"mongodb"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Mongoid does not neutralize a string-typed query criterion supplied to its query builder, and instead passes it to the database as a server-side JavaScript expression. An unauthenticated party able to influence the value an application supplies as a query argument may cause code of their choosing to be evaluated by the database engine. This may result in unintended disclosure of stored field values, unintended selection of documents for application-initiated writes, and reduced database performance.","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":"Server-side JavaScript injection via string query criteria bypassing the strict operator allowlist","id":"CVE-2026-93759","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"NoSQL injection of JavaScript-executing query operators via unsafe-by-default operator guard","id":"CVE-2026-93760"},"packages":[],"prev":{"headline":"Cross-principal document update, theft, and deletion via unvalidated id in nested attributes","id":"CVE-2026-93758"},"products":["Mongoid"],"published":"2026-09-18","related":[{"cvss_score":9.2,"headline":"Data deletion and attribute disclosure via field-name method injection in in-memory queries","id":"CVE-2026-93762","kev_date_added":null,"published":"2026-09-18"},{"cvss_score":8.7,"headline":"Denial of service via unbounded regex matching in Mongoid's in-memory query matcher","id":"CVE-2026-93761","kev_date_added":null,"published":"2026-09-18"},{"cvss_score":8.6,"headline":"Cross-principal document update, theft, and deletion via unvalidated id in nested attributes","id":"CVE-2026-93758","kev_date_added":null,"published":"2026-09-18"},{"cvss_score":8.3,"headline":"NoSQL injection of JavaScript-executing query operators via unsafe-by-default operator guard","id":"CVE-2026-93760","kev_date_added":null,"published":"2026-09-18"},{"cvss_score":8.3,"headline":"Document deletion and process crash via unvalidated method-name dispatch in atomic pop operation","id":"CVE-2026-93765","kev_date_added":null,"published":"2026-09-18"},{"cvss_score":7.1,"headline":"Silent plaintext persistence via unresolved callable database name in encryption schema map","id":"CVE-2026-93763","kev_date_added":null,"published":"2026-09-18"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["MongoDB Inc."]},"summary":"Attackers can inject server-side JavaScript into Mongoid queries, leading to data disclosure and potential code execution on the database.","url":"https://insights.sbomify.com/CVE-2026-93759/"}