Skip to main content
CVE-2025-6707VulnerabilityPublished Updated

CVE-2025-6707: MongoDB Server · Incorrect Authorization

Affects MongoDB ServerSource CVE Database V5

0

Not known to be exploited · CVSS 4.2 Medium · fixed in 8.0.5 : update MongoDB Server when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.0.5, 7.0.21, 6.0.24 +1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade MongoDB Server to 8.0.5, 7.0.21, 6.0.24 or 5.0.31.

Affected software

ProductAffectedFixed in
MongoDB Inc MongoDB ServerAffected
  • =5.0
  • =6.0
  • =7.0
  • =8.0
  • <5.0.31
  • <6.0.24
  • <7.0.21
  • <8.0.5
Fixed in
  • 5.0.31
  • 6.0.24
  • 7.0.21
  • 8.0.5

AI-suggested

Organizations should immediately upgrade MongoDB Server to the fixed versions: 5.0.31 or later, 6.0.24 or later, 7.0.21 or later, and 8.0.5 or later. If you cannot patch yet, administrators should minimize privilege changes during active user sessions and consider temporarily disabling non-essential user accounts. Implement monitoring to detect anomalous access patterns that could indicate exploitation attempts. Regularly audit user privileges and session states to ensure that revoked permissions are enforced promptly. Employ network segmentation and strict access controls to limit authenticated user exposure. Consider integrating MongoDB with external identity and access management (IAM) solutions that provide real-time privilege enforcement. Additionally, review and harden MongoDB authentication and authorization configurations to reduce the attack surface. Document and test incident response plans for potential misuse of stale privileges.

Description

Under certain conditions, an authenticated user request may execute with stale privileges following an intentional change by an authorized administrator. This issue affects MongoDB Server v5.0 version prior to 5.0.31, MongoDB Server v6.0 version prior to 6.0.24, MongoDB Server v7.0 version prior to 7.0.21 and MongoDB Server v8.0 version prior to 8.0.5.

References

Community reviews

Loading reviews…