cve.bz

CVE-2026-120817 Post-authentication race condition in MongoDB Server geospatial schema validation

7.1 highEPSS 0.3%

High (7.1) in mongodb mongodb server. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
A race condition in the schema validation component of MongoDB Server can occur when concurrent writes are checked against a collection validator that uses geospatial query operators. The condition can be caused by an authenticated user with write privileges, and may result in the server terminating unexpectedly.

Severity

CVSS 4.0

7.1 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 26th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
Assigned by
mongodb (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-120817 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120817?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120817?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-120817 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-120817

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-120817](https://cve.bz/cve/badge/CVE-2026-120817.svg)](https://cve.bz/cve/CVE-2026-120817)

HTML:

<a href="https://cve.bz/cve/CVE-2026-120817"><img src="https://cve.bz/cve/badge/CVE-2026-120817.svg" alt="CVE-2026-120817"></a>

Affected

  • mongodb:mongodb server

Versions

From the CNA's record in the CVE List.

ProductAffected
MongoDB Serverfrom 9.0.0 before 9.0.7
MongoDB Serverfrom 8.3.0 before 8.3.16
MongoDB Serverfrom 8.0.0 before 8.0.37
MongoDB Serverfrom 7.0.0 before 7.0.48

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON