CVE-2026-25612: Internal ResourceId collision may affect unrelated collections
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-25612?
The severity of CVE-2026-25612 has not been officially assigned, but it relates to potential resourceId collisions that could lead to unavailability.
How do I fix CVE-2026-25612?
To mitigate CVE-2026-25612, it is advised to upgrade to the latest patch of MongoDB Server that addresses this internal locking mechanism issue.
What types of systems are affected by CVE-2026-25612?
CVE-2026-25612 affects MongoDB Server systems that utilize internal locking for resource management.
What issues can arise from CVE-2026-25612?
CVE-2026-25612 can cause collections to unintentionally collide, resulting in service unavailability.
How can I identify if my MongoDB is vulnerable to CVE-2026-25612?
You can identify if your MongoDB is vulnerable to CVE-2026-25612 by checking if you are using a version that is subject to the internal resourceId collision issue.