Use after free in MongoDB Server may disclose process memory
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- —
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA.
Summary
Use after free in the aggregation feature of MongoDB Server (CWE-416) lets the server read memory after it has been released. When an internal aggregation stage such as $_internalApplyOplogUpdate is combined with a batch size of 0, query results may contain unrelated process memory, and the server process may terminate unexpectedly. An authenticated user with read privileges can trigger this by running an aggregate command that combines these two settings.
Written with Claude Haiku 5.5 from the sources below · 2026-10-27
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| MongoDB | MongoDB Server | 8.3.0 to before 8.3.13; 8.0 to before 8.0.34; 7.0 to before 7.0.45; 9.0 to before 9.0.2 | 8.3.13, 8.0.34, 7.0.45, 9.0.2 | Patch available | CNA |
- MongoDB Server VendorMongoDB Affected 8.3.0 to before 8.3.13; 8.0 to before 8.0.34; 7.0 to before 7.0.45; 9.0 to before 9.0.2 Fixed in 8.3.13, 8.0.34, 7.0.45, 9.0.2 Patch available CNA
Remediation
Upgrade MongoDB Server to 8.3.13, 8.0.34, 7.0.45 or 9.0.2. Affected ranges are from 8.3.0 before 8.3.13, from 8.0 before 8.0.34, from 7.0 before 7.0.45 and from 9.0 before 9.0.2.
Written with Claude Haiku 5.5 from the sources below · 2026-10-27
- Fix · CNA MongoDB Server (MongoDB) Fixed in 8.3.13, 8.0.34, 7.0.45, 9.0.2
Timeline
- 2026-10-13 Threatist record created from CVE-2026-96297
- 2026-10-13 CISA SSVC decision points changed
- 2026-10-13 Priority changed: MEDIUM → LOW
- 2026-10-13 Alias added: GHSA-8hjj-9fm5-xw5g
References
More MongoDB vulnerabilities
- TI-2019-08023 Code injection in mongo-express KEVCVSS 3.1CRITICAL 9.9
- TI-2025-13542 Zlib compressed protocol header length confusion may allow memory read KEVCVSS 4.0HIGH 8.7
- TI-2026-79432 BSON output corruption via out-of-range binary subtype in MongoDB C# Driver CVSS 4.0MEDIUM 6.9
- TI-2026-79424 NoSQL command injection via mismatched BSON length in MongoDB C# Driver CVSS 4.0MEDIUM 6.9
- TI-2026-79422 Unbounded memory growth in MongoDB C# Driver BSON deserialization CVSS 4.0HIGH 8.2
- TI-2026-79427 Authentication bypass via issuer-and-serial-only certificate equality CVSS 4.0HIGH 7.6
Sources
- CVE-2026-96297 · CVE Program
- CVE-2026-96297 · NVD
- FIRST EPSS
- GHSA-8hjj-9fm5-xw5g · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences