CVE-2021-32040
No exploitation reported by the sources we read.
- Published2022-04-12
- Fixed in5.0.4 · 4.4.11 · 4.2.16
- WeaknessCWE-121 · CWE-787
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
It may be possible to have an extremely long aggregation pipeline in conjunction with a specific stage/operator and cause a stack overflow due to the size of the stack frames used by that stage. If an attacker could cause such an aggregation to occur, they could maliciously crash MongoDB in a DoS attack. This vulnerability affects MongoDB Server v4.4 versions prior to and including 4.4.28, MongoDB Server v5.0 versions prior to 5.0.4 and MongoDB Server v4.2 versions prior to 4.2.16. Workaround: >= v4.2.16 users and all v4.4 users can add the --setParameter internalPipelineLengthLimit=50 instead of the default 1000 to mongod at startup to prevent a crash.
Timeline
dates in UTC- 2022-04-1215:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2021-32040?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2021-32040?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · CISA-ADP| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 5.0 | ≥ 5.0.0, < 5.0.4 | 5.0.4 | NVD |
| 5.0 | ≥ 5.0, < 5.0.4 | 5.0.4 | CISA-ADP |
| 4.4 | ≥ 4.4.0, < 4.4.11 | 4.4.11 | NVD |
| 4.2 | ≥ 4.2.0, < 4.2.16 | 4.2.16 | NVD |
| 4.2 | ≥ 4.2, < 4.2.16 | 4.2.16 | CISA-ADP |
| 4.4 | ≥ 4.4, ≤ 4.4.28 | no fix published | CISA-ADP |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update MongoDB to 5.0.4 · 4.4.11 · 4.2.16
Advisories and patches
- jira.mongodb.orgPatch · Vendor Advisory
- jira.mongodb.orgPatch · Vendor Advisory
- jira.mongodb.orgPatch · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2022-04-12
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2021-32040?
Is CVE-2021-32040 actively exploited?
What is the CVSS score for CVE-2021-32040?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.