CVE-2026-114644 MongoDB CVE debrief

Who should care

Defenders responsible for MongoDB C# Driver deployments should assess exposure and prioritize updates to mitigate potential memory-exhaustion denial of service attacks. This includes reviewing application code, implementing monitoring, and verifying the version of the MongoDB C# Driver in use. Additionally, defenders should consider compensating controls for exposed systems and track exceptions and retest remediated assets.

Why it matters

CVE-2026-114644 is a high-severity vulnerability in the MongoDB C# Driver that can lead to memory-exhaustion denial of service attacks. Defenders should prioritize verifying and updating affected deployments to mitigate potential risks.

• Memory exhaustion leading to denial of service
• Potential for unauthenticated remote attacks
• Need for version verification and updates
• Limited information on specific exploitation instances

Technical summary

The MongoDB C# Driver's BSON library contains an uncontrolled resource consumption weakness in its deserialization handling of one BSON value type. An application that deserializes untrusted content with the library retains data derived from that content for the lifetime of the process, with no limit on how much accumulates. This weakness can be exploited by an unauthenticated remote party to cause unbounded memory growth, leading to a denial of service. The vulnerability affects the MongoDB C# Driver and can be mitigated by updating to version 3.13.0 or later. It is essential to review application code to ensure proper handling of untrusted BSON/JSON content and implement monitoring to detect potential memory

Defensive priority

Defenders should prioritize verifying and updating to version 3.13.0 or later of the MongoDB C# Driver to mitigate this vulnerability.

Recommended defensive actions

• Verify the version of the MongoDB C# Driver in use and update to version 3.13.0 or later if necessary.
• Review application code to ensure proper handling of untrusted BSON/JSON content.
• Implement monitoring to detect potential memory exhaustion attacks.
• 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 source item provide details on the vulnerability, its impact, and affected versions. However, the corpus does not establish specific exploitation instances or remediation beyond updating to version 3.13.0 or later.

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.