MongoDB Server up to 7.0.28/8.0.17/8.2.3 Internal Locking unrestricted externally accessible lock
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in MongoDB Server up to 7.0.28/8.0.17/8.2.3. This vulnerability affects unknown code of the component Internal Locking. This manipulation causes unrestricted externally accessible lock. This vulnerability is tracked as CVE-2026-25612. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in MongoDB Server up to 7.0.28/8.0.17/8.2.3. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component Internal Locking. The manipulation with an unknown input leads to a unrestricted externally accessible lock vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect availability. The summary by CVE is:
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.
The advisory is shared at jira.mongodb.org. This vulnerability is known as CVE-2026-25612 since 02/03/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 298784 (Linux Distros Unpatched Vulnerability : CVE-2026-25612), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 7.0.29, 8.0.18 or 8.2.4 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (298784) and CERT Bund (WID-SEC-2026-0386). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Open Source MongoDB
Product
Type
Vendor
Name
Version
- 7.0.0
- 7.0.1
- 7.0.2
- 7.0.3
- 7.0.4
- 7.0.5
- 7.0.6
- 7.0.7
- 7.0.8
- 7.0.9
- 7.0.10
- 7.0.11
- 7.0.12
- 7.0.13
- 7.0.14
- 7.0.15
- 7.0.16
- 7.0.17
- 7.0.18
- 7.0.19
- 7.0.20
- 7.0.21
- 7.0.22
- 7.0.23
- 7.0.24
- 7.0.25
- 7.0.26
- 7.0.27
- 7.0.28
- 8.0.0
- 8.0.1
- 8.0.2
- 8.0.3
- 8.0.4
- 8.0.5
- 8.0.6
- 8.0.7
- 8.0.8
- 8.0.9
- 8.0.10
- 8.0.11
- 8.0.12
- 8.0.13
- 8.0.14
- 8.0.15
- 8.0.16
- 8.0.17
- 8.2.0
- 8.2.1
- 8.2.2
- 8.2.3
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (mongodb): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Unrestricted externally accessible lockCWE: CWE-412 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 298784
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-25612
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Server 7.0.29/8.0.18/8.2.4
Timeline
02/03/2026 CVE reserved02/10/2026 Advisory disclosed
02/10/2026 VulDB entry created
02/16/2026 VulDB entry last update
Sources
Advisory: jira.mongodb.orgStatus: Confirmed
CVE: CVE-2026-25612 (🔒)
GCVE (CVE): GCVE-0-2026-25612
GCVE (VulDB): GCVE-100-345337
CERT Bund: WID-SEC-2026-0386 - MongoDB Server, Go Driver, Ruby Driver: Mehrere Schwachstellen
Entry
Created: 02/10/2026 19:58Updated: 02/16/2026 05:26
Changes: 02/10/2026 19:58 (76), 02/11/2026 12:14 (7), 02/16/2026 05:26 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.