CVE-2026-25612
Awaiting Analysis Awaiting Analysis - Queue
Lock Collision Deadlock in MongoDB Server Causes Service Unavailability

Publication date: 2026-02-10

Last updated on: 2026-02-10

Assigner: MongoDB, Inc.

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-10
Last Modified
2026-02-10
Generated
2026-06-16
AI Q&A
2026-02-10
EPSS Evaluated
2026-06-14
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
mongodb mongodb *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-412 The product properly checks for the existence of a lock, but the lock can be externally controlled or influenced by an actor that is outside of the intended sphere of control.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability involves the internal locking mechanism of the MongoDB server. The server uses an internal encoding of resources to determine which lock to acquire. However, collections may unintentionally collide in this encoding, causing conflicting locks between them.

As a result, these collisions can lead to unavailability issues because the conflicting locks prevent normal access to the collections.

Impact Analysis

The primary impact of this vulnerability is unavailability of MongoDB collections. Due to conflicting locks caused by the internal encoding collision, collections may become inaccessible or experience downtime.

This can disrupt applications relying on MongoDB for data storage and retrieval, potentially causing service interruptions.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

I don't know

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-25612. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart