CVE-2026-96297
6.5MediumPublished 13 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Impact
- High impact on confidentiality
- Weakness
- CWE-416
Impact
Authenticated users with read access can read unauthorized memory from the server process or crash the database. They only need standard query permissions to run a malicious aggregation query.
Root cause
A use-after-free bug in MongoDB's aggregation engine occurs when processing an internal stage with a batch size of zero.
Affected systems
Versions not listed — check the vendor advisory.
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Fix & remediation
Upgrade MongoDB Server to the patched release referenced in SERVER-132946 once available; no interim configuration workaround is provided.
$ mongod --versionAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
Use of freed memory in the aggregation feature of MongoDB Server can cause the server to read data from a memory area after it has been released. When an internal aggregation stage is combined with a batch size of 0, the server may read from memory that is no longer in use. Because that memory can be reused for other data before it is read, query results returned to the client may contain unrelated data from the server process. Depending on the state of memory at the time, the server process may also terminate unexpectedly. The behavior can occur when an authenticated user with read privileges runs an aggregate command that combines these two settings.