Is MongoDB 3.2.22 patched?
Current stable (8.3.4): 100/100
3.2.22 has 1 open critical-or-high vulnerability. Run 7.0.35 or later to clear it. See what 7.0.35 fixes →
Summary iPlain-English security status for MongoDB 3.2.22, built from its CVEs, active-exploitation data, end-of-life date and latest release.
MongoDB 3.2.22 is part of the 3.2 release line. 1 known vulnerability affects it. The minimum safe version is 7.0.35 — upgrade to it or later to clear the open critical/high issues. The 3.2 line reached end-of-life on 2018-09-30, so it no longer receives security patches. The latest supported MongoDB release is 8.3.4.
Known issues affecting 3.2.22
Exploited first, then by exploitation probability.
CVE-2026-9753 HIGH EPSS 0% → fixed in 8.3.3Other MongoDB versions
Check another release line of MongoDB.
Frequently asked
Is MongoDB 3.2.22 patched?
MongoDB 3.2.22 is end-of-life and no longer receives security patches. Move to 8.3.4.
What version should I upgrade MongoDB 3.2.22 to?
Upgrade MongoDB 3.2.22 to at least 7.0.35 to clear its 1 open critical-or-high vulnerability.
When does MongoDB 3.2 reach end-of-life?
MongoDB 3.2 reached end-of-life on 2018-09-30 and no longer receives security patches.
What is the latest version of MongoDB?
The latest supported MongoDB release is 8.3.4.
Is MongoDB 3.2.22 still receiving security updates?
No — MongoDB 3.2.22 is on the 3.2 line, which reached end-of-life on 2018-09-30 and no longer receives security updates. Upgrade to 8.3.4 or later to stay supported.
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against MongoDB's official advisory before you patch or upgrade — MongoDB official site ↗