GPU VulnDB

Database/Control plane, storage & DevOps

MongoDB Server: use-after-free in query memory tracking crashes or corrupts the server process

CVSS 7.2CVE-2026-82061Control plane, storage & DevOpscurated

Impact

An authenticated user with nothing more than read privileges can drive the query execution memory tracking subsystem into writing to freed heap memory using ordinary database commands. The stated outcome is a crash of the server process, with potential memory corruption beyond that. Where MongoDB backs a cluster control plane - job metadata, tenant records, model or dataset catalogues - a read-only account held by any tenant-facing service becomes an availability lever over scheduling and admission, and a crashed primary forces a replica set election. The record scores it 7.2 with high integrity and availability impact and no confidentiality loss; no user interaction is needed.

Who can reach it

Any authenticated MongoDB user holding read privileges on the server, reachable over the network wherever the database listens. No elevated role and no user interaction required.

What to do

Upgrade to the fixed MongoDB Server release tracked in SERVER-130907; the record does not name the fixed versions, so take them from the MongoDB advisory for your major branch. Applying it is a rolling restart of replica set or shard members rather than a node reboot. Until then, audit which accounts hold read access and cut off untrusted or tenant-facing credentials, since read privilege is the entire precondition.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.