CVE-2026-25609: MongoDB Server · Missing Authorization
Affects MongoDB ServerSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium · fixed in 8.2.4 : update MongoDB Server when convenient.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.2.4, 8.0.18, 7.0.29
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.2.4, 8.0.18 or 7.0.29.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MongoDB IncMongoDB Server | Affected
| Fixed in
|
AI-suggested
1. Monitor MongoDB server logs for unusual or unauthorized 'profile' command usage, especially changes to the 'filter' parameter. 2. Restrict network access to MongoDB instances using firewalls and VPNs to limit exposure to trusted users only. 3. Implement strict role-based access control (RBAC) policies, ensuring that only authorized administrators can modify profiling settings. 4. Regularly audit user privileges and remove unnecessary low-privilege accounts that could exploit this vulnerability. 5. Apply vendor patches promptly once available; in the absence of patches, consider disabling profiling or restricting its modification until a fix is released. 6. Employ intrusion detection systems (IDS) and security information and event management (SIEM) tools to detect anomalous behavior related to profiling commands. 7. For cloud deployments, leverage provider security controls to isolate and monitor MongoDB instances. 8. Educate database administrators about this vulnerability and best practices for secure MongoDB configuration.
Description
Incorrect validation of the profile command may result in the determination that a request altering the 'filter' is read-only.