CVE-2025-6711 json
Incomplete Redaction of Sensitive Information in MongoDB Server Logs
published last yr. modified last mo. also BIT-mongodb-2025-6711 , EUVD-2025-20248
- cvss
- 4.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 20%
- public exploits
- 0
- none known
Summary
An issue has been identified in MongoDB Server where unredacted queries may inadvertently appear in server logs when certain error conditions are encountered. This issue affects MongoDB Server v8.0 versions prior to 8.0.5, MongoDB Server v7.0 versions prior to 7.0.18 and MongoDB Server v6.0 versions prior to 6.0.21.
Patch / fix
- bitnami mongodb 6.0.21, 7.0.18, 8.0.5
- MongoDB Inc MongoDB Server 6.0.21, 7.0.18, 8.0.5
Is CVE-2025-6711 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.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.4 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 4.4 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | mongodb | >=6.0.0, <6.0.21 >=7.0.0, <7.0.18 >=8.0.0, <8.0.5 |
6.0.21 7.0.18 8.0.5 |
Affected products
- MongoDB Inc MongoDB Server
Classification
- Weakness
-
- CWE-532 Insertion of Sensitive Information into Log File
- Technology feeds
References
-
jira.mongodb.org
/browse/SERVER-98720
issue-tracking, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-6711
web
Sources
- CVE List CVE-2025-6711
- NVD CVE-2025-6711
- OSV BIT-mongodb-2025-6711
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.