CVE-2026-4148
Use-After-Free in MongoDB Sharded Clusters via $lookup Aggregation
Publication date: 2026-03-17
Last updated on: 2026-04-10
Assigner: MongoDB, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mongodb | mongodb | 8.3.0 |
| mongodb | mongodb | From 7.0.0 (inc) to 7.0.31 (exc) |
| mongodb | mongodb | From 8.0.0 (inc) to 8.0.20 (exc) |
| mongodb | mongodb | From 8.2.0 (inc) to 8.2.6 (exc) |
| mongodb | mongodb | 8.3.0 |
| mongodb | mongodb | 8.3.0 |
| mongodb | mongodb | 8.3.0 |
| mongodb | mongodb | 8.3.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a use-after-free issue that can be triggered in sharded clusters of MongoDB. It requires an authenticated user who has the read role to issue a specially crafted $lookup or $graphLookup aggregation pipeline, which then exploits the flaw.
How can this vulnerability impact me? :
The vulnerability has a high severity score (CVSS v3.1 BaseScore 8.8), indicating it can have significant impact. It can lead to unauthorized actions such as data corruption, data leakage, or denial of service due to the use-after-free condition triggered by a low-privileged authenticated user.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know