CVE-2026-13072
Awaiting Analysis Awaiting Analysis - Queue

Memory Corruption in MongoDB Aggregation Pipeline

Vulnerability report for CVE-2026-13072, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-22

Last updated on: 2026-07-24

Assigner: MongoDB, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-22
Last Modified
2026-07-24
Generated
2026-08-12
AI Q&A
2026-07-22
EPSS Evaluated
2026-08-10
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
mongodb mongodb *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-122 A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability occurs in MongoDB when compute mode is enabled on a standalone mongod instance. It involves insufficient validation of BSON data from external sources during aggregation pipeline processing, which can lead to memory corruption. This may cause the process to terminate or behave unpredictably. The compute mode setting is not enabled by default and must be explicitly configured at startup.

Detection Guidance

Detection requires checking if compute mode is enabled on a standalone mongod instance. Use the command: mongod --help | grep computeMode to verify if the flag is present. If enabled, review aggregation pipeline inputs for externally sourced BSON data to identify potential memory corruption risks.

Impact Analysis

The impact includes potential process crashes or unintended behavior due to memory corruption. An attacker could exploit this to disrupt database operations or gain unauthorized access if they can submit maliciously crafted BSON data. Since the compute mode is non-default, only systems with this specific configuration are at risk.

Compliance Impact

This vulnerability involves memory corruption in MongoDB due to insufficient validation of BSON data during aggregation processing. While not directly tied to compliance standards, such vulnerabilities could potentially lead to unauthorized data access or integrity issues, which may impact GDPR (data protection) or HIPAA (health data security) compliance if exploited.

Mitigation Strategies

Disable compute mode on standalone mongod instances if enabled. Ensure no external BSON data is processed in aggregation pipelines. Restart mongod with default settings if compute mode was active.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-13072. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart