CVE-2026-13075 MongoDB CVE debrief

Who should care

MongoDB administrators and defenders should assess exposure and prioritize patching for versions 8.2.0 to 8.2.12 and 8.3.0 to 8.3.7. They should also verify the affected versions and apply patches to prevent potential exploitation. Additionally, defenders should review compensating controls for exposed systems, monitor instance performance and logs, and track exceptions and remediation efforts.

Why it matters

Defenders should prioritize patching MongoDB versions 8.2.0 to 8.2.12 and 8.3.0 to 8.3.7 to prevent potential DoS and data loss due to this vulnerability.

• Potential denial of service (DoS) due to mongod process termination
• Increased risk of data loss or corruption if not properly patched
• Need for verification of affected versions and application of patches

Technical summary

The vulnerability allows an authenticated user to cause the mongod process to terminate under memory pressure via specific aggregation stages ($rankFusion and $scoreFusion). The issue originates in the server's error-handling path and requires the ability to run aggregation queries. This vulnerability affects MongoDB versions 8.2.0 to 8.2.12 and 8.3.0 to 8.3.7, potentially leading to denial of service (DoS) and data loss if not properly patched. Defenders should prioritize verifying and applying patches for these versions.

Defensive priority

Defenders should prioritize verifying and applying patches for MongoDB versions 8.2.0 to 8.2.12 and 8.3.0 to 8.3.7, as an authenticated user can cause the mongod process to terminate under memory pressure.

Recommended defensive actions

• Verify and apply patches for MongoDB versions 8.2.0 to 8.2.12 and 8.3.0 to 8.3.7
• Restrict access to aggregation query functionality to trusted users
• Monitor MongoDB instance performance and logs for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. The vulnerability allows an authenticated user to cause the mongod process to terminate under memory pressure via specific aggregation stages. MongoDB administrators and defenders should verify the affected versions and apply patches to prevent potential exploitation. The issue requires the ability to run aggregation queries, and defenders should prioritize verifying and applying patches for MongoDB versions

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.