{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-93764 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-93764 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-93764 is a high-severity vulnerability in MongoDB Inc. Mongoid, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93764 and fix it if it is affected.\n\nWhat it is: CVE-2026-93764 is a high-severity vulnerability in MongoDB Inc. Mongoid, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-93764 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-93764/ (Markdown: https://insights.sbomify.com/CVE-2026-93764/index.md)","id":"CVE-2026-93764","markdown":"https://insights.sbomify.com/CVE-2026-93764/index.md","name":"CVE-2026-93764","record":{"aliases":["GHSA-p3g7-qcr8-3pgm"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Mongoid Ruby ODM","requires_auth":"low_privilege","summary":"Mongoid may store encrypted fields in plaintext if embedded models are skipped, exposing sensitive data to anyone with database access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mongodb","cpe":[{"product":"mongoid","vendor":"mongodb"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"Mongoid may omit encryption rules for fields declared on embedded models when generating the client-side field-level encryption schema. Applications that enable this feature can therefore store values intended to be encrypted in readable form, with no error or warning. A party with routine read access to the database, a backup, or the underlying data files may then see data that was meant to remain unreadable outside the application.","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":"Plaintext storage of encrypted fields via skipped embedded models in encryption schema generation","id":"CVE-2026-93764","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Document deletion and process crash via unvalidated method-name dispatch in atomic pop operation","id":"CVE-2026-93765"},"packages":[],"prev":{"headline":"Silent plaintext persistence via unresolved callable database name in encryption schema map","id":"CVE-2026-93763"},"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.8,"headline":"Server-side JavaScript injection via string query criteria bypassing the strict operator allowlist","id":"CVE-2026-93759","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["MongoDB Inc."]},"summary":"Mongoid may store encrypted fields in plaintext if embedded models are skipped, exposing sensitive data to anyone with database access.","url":"https://insights.sbomify.com/CVE-2026-93764/"}