{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-25612 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-25612 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25612 is a high-severity vulnerability in MongoDB Server, published on 10 Feb 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-25612 and fix it if it is affected.\n\nWhat it is: CVE-2026-25612 is a high-severity vulnerability in MongoDB Server, published on 10 Feb 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-25612 in the wild and no public exploit code.\n\nAffected product: MongoDB Server. 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-25612/ (Markdown: https://insights.sbomify.com/CVE-2026-25612/index.md)","id":"CVE-2026-25612","markdown":"https://insights.sbomify.com/CVE-2026-25612/index.md","name":"CVE-2026-25612","record":{"aliases":["GHSA-c488-mfgm-vqrf","UBUNTU-CVE-2026-25612"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MongoDB Server","requires_auth":"low_privilege","summary":"An internal resource ID collision in MongoDB's locking mechanism can cause unrelated collections to conflict, leading to service unavailability.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mongodb","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-412","name":"Unrestricted Externally Accessible Lock"}],"description":"The internal locking mechanism of the MongoDB server uses an internal encoding of the resources in order to choose what lock to take. Collections may inadvertently collide with one another in this representation causing unavailability between them due to conflicting locks.","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":"Internal ResourceId collision may affect unrelated collections","id":"CVE-2026-25612","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"An unsafe cast in the MongoDB query planner can result in a segmentation fault.","id":"CVE-2026-25613"},"packages":[],"prev":{"headline":"Pre-Authentication Memory Exhaustion Denial of Service in MongoDB Server","id":"CVE-2026-25611"},"products":["MongoDB Server"],"published":"2026-02-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-02-10","vendors":["MongoDB Inc"]},"summary":"An internal resource ID collision in MongoDB's locking mechanism can cause unrelated collections to conflict, leading to service unavailability.","url":"https://insights.sbomify.com/CVE-2026-25612/"}