CVE-2025-6714 json
Incorrect Handling of incomplete data may prevent mongoS from Accepting New Connections
published last yr. modified 2mo ago also BIT-mongodb-2025-6714 , EUVD-2025-20263
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
MongoDB Server's mongos component can become unresponsive to new connections due to incorrect handling of incomplete data. This affects MongoDB when configured with load balancer support. This issue affects MongoDB Server v6.0 prior to 6.0.23, MongoDB Server v7.0 prior to 7.0.20 and MongoDB Server v8.0 prior to 8.0.9
Required Configuration:
This affects MongoDB sharded clusters when configured with load balancer support for mongos using HAProxy on specified ports.
Patch / fix
- bitnami mongodb 6.0.23, 7.0.20, 8.0.9
- MongoDB Inc MongoDB Server 6.0.23, 7.0.20, 8.0.9
Is CVE-2025-6714 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | mongodb | >=6.0.0, <6.0.23 >=7.0.0, <7.0.20 >=8.0.0, <8.0.9 |
6.0.23 7.0.20 8.0.9 |
Affected products
- MongoDB Inc MongoDB Server
Classification
- Weakness
- Technology feeds
References
-
jira.mongodb.org
/browse/SERVER-106753
issue-tracking, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-6714
web
Sources
- CVE List CVE-2025-6714
- NVD CVE-2025-6714
- OSV BIT-mongodb-2025-6714
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.