MongoDB post-auth code execution in time-series bucket validation
Affects MongoDB Server time-series collection writes that reach the strict bucket validator, for users with insert privileges. Fixed in 8.3.16, 9.0.7, 8.0.37, and 7.0.48.
- Exploited
- No known exploitation
- Fix
- Fixed in 9.0.7, 8.3.16, 8.0.37, 7.0.48
- Who is exposed
- Specific setups only
Summary
The flaw is in MongoDB Server's time-series collection component and can be reached remotely by a user who has logged in with low-level privileges, such as the ability to write bucket documents directly. Successful exploitation can crash the server or, under certain conditions, allow arbitrary code execution in the server process.
Written by a model
Original description
A use-after-free in the time-series collection component of MongoDB Server can occur when the server validates a time-series bucket document during a write. The condition can be caused by an authenticated user with privileges to write bucket documents directly, and may result in the server terminating unexpectedly or, under certain conditions, arbitrary code execution in the context of the server process.
Who should check
Teams running MongoDB Server 8.0.28+, 8.2.12+, 8.3.3+, or 9.0.0+ that have time-series collections and let authenticated users insert data
“Affects 8.0.28+, 8.2.12+, 8.3.3+, 9.0.0+”
What to do
Check whether your setup matches what the bug needs.
MongoDB Server versions 8.0.28+, 8.2.12+, 8.3.3+, or 9.0.0+ (7.0 not affected via the strict-validation path) Time-series collection writes reach the strict bucket validator, which runs by default on raw bucket inserts and updates Requires an authenticated user with insert privileges on a time-series collectionUpgrade to a fixed version: 9.0.7, 8.3.16, 8.0.37, 7.0.48.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-120824 (Post-authentication use-after-free in MongoDB Server time-series bucket validation), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-120824 (entry last updated 2026-11-13):
Affected:
- MongoDB MongoDB Server: from 9.0.0, fixed in 9.0.7; from 8.3.0, fixed in 8.3.16; from 8.0.0, fixed in 8.0.37; from 7.0.0, fixed in 7.0.48
Fixed versions: 9.0.7, 8.3.16, 8.0.37, 7.0.48.
Conditions (all must be true for the bug to be hit):
- MongoDB Server versions 8.0.28+, 8.2.12+, 8.3.3+, or 9.0.0+ (7.0 not affected via the strict-validation path) (source: https://jira.mongodb.org/browse/SERVER-136505)
- Time-series collection writes reach the strict bucket validator, which runs by default on raw bucket inserts and updates (source: https://jira.mongodb.org/browse/SERVER-136505)
- Requires an authenticated user with insert privileges on a time-series collection (source: https://jira.mongodb.org/browse/SERVER-136505)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-120824 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120824 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://jira.mongodb.org/browse/SERVER-136505
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-120824
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120824"}.Affected versions
- MongoDB MongoDB ServerFrom 9.0.0 · fixed in 9.0.7; From 8.3.0 · fixed in 8.3.16; From 8.0.0 · fixed in 8.0.37; From 7.0.0 · fixed in 7.0.48
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach17/20Affects MongoDB (a widely deployed server, runtime, framework or database)
- Severity9.7/10CVSS 8.7, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 85 if added to CISA KEV
- Would score about 80 if CISA's SSVC rates exploitation active
- Would score about 42 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now3 days
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Public exploit activity
- EPSS: 0.61%
- Posted on X by cve.now Nov 10
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | jira.mongodb.org · browse/SERVER-136505 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-120824 |
| Record | NVD · CVE-2026-120824 |
Questions about CVE-2026-120824
Is CVE-2026-120824 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A use-after-free in MongoDB Server's time-series bucket validation corrupts heap memory in the mongod process, which can crash the server. An external reporter also demonstrates escalation to arbitrary command execution with the privileges of the mongod OS user.
Source: jira.mongodb.org
Which versions are affected by CVE-2026-120824?
MongoDB Server: from 9.0.0 before 9.0.7; from 8.3.0 before 8.3.16; from 8.0.0 before 8.0.37; from 7.0.0 before 7.0.48.
Source: cve.now feed data
How do I fix CVE-2026-120824?
Upgrade to a fixed version: 8.3.16, 9.0.7, 8.0.37, or 7.0.48, matching your release line.
Source: jira.mongodb.org
Related
- CVE-2026-118383Pre-authentication use-after-free in MongoDB Server replica set primary catch-up
- CVE-2026-120808Certificate Validation Bypass via IPv6 trust-result skip in macOS TLS client
- CVE-2026-120828Memory exhaustion via abandoned far-future read-concern waiters in disaggregated storage
- CVE-2026-120822Missing Authorization Check in MongoDB Server Replication-Related Administrative Command Leads to Unauthorized Data Access
- CVE-2026-120815Incorrect Authorization Check in MongoDB Server Localhost Exception Leads to Unauthorized Administrative Access
- CVE-2026-120813Plaintext storage of encrypted fields via duplicate keys in client-side encryption schema parsing
No corrections so far. Something wrong on this page? Report an error.