{"id":"CVE-2026-96297","title":"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","summary":"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 …","severity":"medium","cvss":6.5,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","cwe":["CWE-416"],"published":"2026-10-13","updated":"2026-10-13","sourceUpdated":"2026-10-13T17:17:49.290","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-96297","references":[{"url":"https://jira.mongodb.org/browse/SERVER-132946","label":"cna@mongodb.com"}],"tags":["nvd"],"ingestedAt":"2026-10-13T16:35:46.746Z","slug":"CVE-2026-96297","body":"## Overview\n\nUse 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.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":36,"depthScoreParts":{"impact":35.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}