Medium severity · published Oct 13, 2026
CVE-2026-96299
Missing Authorization Check on Internal Aggregation Stage in MongoDB Server mongos Leads to Denial of Service
6.5
CVSS
0.2%
EPSS
No
On KEV
Description
A security issue was discovered in MongoDB mongos (the sharded cluster router) where an authenticated user with readWrite privileges could crash the mongos process by crafting a specially formed aggregation pipeline. The issue leverages an internal aggregation stage that lacks proper authorization checks despite being intended for internal use, allowing a subsequent stage to be forced to execute on the router under conditions it was not designed to handle. This results in an unhandled fatal error that causes the mongos process to immediately abort, resulting in denial of service for all clients routed through the affected mongos instance.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
None
Integrity
None
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 14% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
MO
MongoDB · MongoDB
8.3.0 before 8.3.13; 9.0 before 9.0.4 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-96299
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-96299
jira.mongodb.org
https://jira.mongodb.org/browse/SERVER-130431
More from MongoDB
9.9
CVE-2019-10758
MongoDB mongo-express Remote Code Execution Vulnerability
7.5
CVE-2025-14847
Zlib compressed protocol header length confusion may allow memory read
9.8
CVE-2026-19001
MongoDB BI Connector ODBC driver may write outside an allocated buffer when handling oversized catalog object names
9.8
CVE-2025-3085
A MongoDB server under specific conditions running on Linux with TLS and CRL revocation status checking enabled, fails to check the revocation status of the intermediate…
9.8
CVE-2024-8654
MongoDB Server may access non-initialized region of memory leading to unexpected behaviour
