MongoDB Server up to 6.0.20/7.0.17/8.0.4 log file

Summaryinfo

A vulnerability was found in MongoDB Server up to 6.0.20/7.0.17/8.0.4. It has been classified as problematic. Affected by this issue is some unknown functionality. The manipulation leads to log file. This vulnerability is listed as CVE-2025-6711. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in MongoDB Server up to 6.0.20/7.0.17/8.0.4. This issue affects an unknown code block. The manipulation with an unknown input leads to a log file vulnerability. Using CWE to declare the problem leads to CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. Impacted is confidentiality. The summary by CVE is:

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.

The advisory is shared at jira.mongodb.org. The identification of this vulnerability is CVE-2025-6711 since 06/26/2025. The exploitation is known to be difficult. The attack may be initiated remotely. Additional levels of successful authentication are necessary for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 264345 (Linux Distros Unpatched Vulnerability : CVE-2025-6711), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.0.21, 7.0.18 or 8.0.5 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (264345). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Database Software

Vendor

• MongoDB

Name

• Server

Version

• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5
• 6.0.6
• 6.0.7
• 6.0.8
• 6.0.9
• 6.0.10
• 6.0.11
• 6.0.12
• 6.0.13
• 6.0.14
• 6.0.15
• 6.0.16
• 6.0.17
• 6.0.18
• 6.0.19
• 6.0.20
• 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
• 8.0.0
• 8.0.1
• 8.0.2
• 8.0.3
• 8.0.4

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion