Cyber Resilience

CVE-2026-8199

Mongodb 7.0.0 – 7.0.34

Published
13 May 2026
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v4 7.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0026 17th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-8199 is a high-severity Improperly Controlled Sequential Memory Allocation (CWE-1325) vulnerability in Mongodb Mongodb. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 17th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-6 (Resource Availability) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

An authenticated user can cause excess memory usage via bitwise match expression AST processing of $bitsAllSet, $bitsAnySet, $bitsAllClear, and $bitsAnyClear. This contributes to memory pressure and may lead to availability loss by OOM. This issue impacts MongoDB Server v7.0 versions…

more

prior to 7.0.34, v8.0 versions prior to 8.0.23, v8.2 versions prior to 8.2.9 and v8.3 versions prior to 8.3.2.

CWE(s)
CWE-1325

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
attack.mitre.org →
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-13056Same product: Mongodb Mongodb
CVE-2026-13064Same product: Mongodb Mongodb
CVE-2026-9740Same product: Mongodb Mongodb
CVE-2025-6710Same product: Mongodb Mongodb
CVE-2026-1849Same product: Mongodb Mongodb
CVE-2025-6714Same product: Mongodb Mongodb
CVE-2025-6712Same product: Mongodb Mongodb
CVE-2025-13644Same product: Mongodb Mongodb
CVE-2026-9748Same product: Mongodb Mongodb
CVE-2026-9747Same product: Mongodb Mongodb

Affected Assets

mongodb
mongodb
7.0.0 — 7.0.34 · 8.0.0 — 8.0.23 · 8.2.0 — 8.2.9

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V2.4.1
  • V13.1.2
  • V13.2.6

Mitigating Controls (NIST 800-53 r5) AI

SC-6 Resource Availability good match

SC-6 directly enforces resource quotas and priority allocations that stop unbounded sequential memory requests from exhausting the system.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require developers to enforce total memory limits during sequential allocations.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect unbounded allocation patterns, but removing the weakness does not fulfill testing obligations.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle includes resource-management requirements that can prevent uncontrolled per-object allocations.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles can mandate bounded resource usage, but eliminating this CWE does not address broader architectural controls.

A.8.28 Secure coding partial match
prevents

Secure coding standards can require explicit limits on memory per object, yet fixing the weakness alone does not satisfy the full control.

A.8.6 Capacity management partial match
mitigates

Capacity management directly limits total memory consumption across objects, mitigating unbounded sequential allocations.

References