MONGODB · CVE-2026-120803 · Runtime
NO FIX YET
A use-after-free in MongoDB's Slot-Based Execution window function accumulator, used by certain $setWindowFields pipelines, lets a stale pointer be read during serialization. An attacker can read adjacent heap contents and crash the mongod server.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only deployments where users with readWrite privileges on a database can submit aggregation pipelines to mongod, since the flaw is reached by crafting a specific $setWindowFields pipeline. Deployments that restrict who can run aggregations or that do not expose the database to untrusted users face lower risk. The sources do not list the affected version ranges.
Not affected if auth-required, managed-hosting
Who cares database, mongodb, self-hosted
mongod --version and compare it against the fixed versions in the MongoDB advisory$setWindowFields if you have application logs or query audit dataUnknown from the sources.
A use-after-free issue exists in MongoDB’s SBE (Slot-Based Execution) implementation of a window function accumulator used by certain $setWindowFields aggregation pipelines. Under specific conditions, the accumulator can retain a dangling pointer to memory that has since been freed. When this stale pointer is later dereferenced during serialization of the carried-forward value, it can result in a heap out-of-bounds read that may expose adjacent heap contents and crash the mongod server. An authenticated user with readWrite privileges on a database can trigger this issue by crafting a specific aggregation pipeline.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.