MongoDB 4.4 end of life
MongoDB 4.4 reached end of life on 29 February 2024. It is the last MongoDB line that runs on x86_64 CPUs without AVX, which is why so many deployments remain on it. MongoDB has published occasional post-EOL releases, most recently 4.4.31 in June 2026, but makes no commitment to continue.
- End of life
- 29 February 2024
- Released
- Jul 2020
- Final release
- 4.4.31 (latest known, June 2026)
- Successor
- MongoDB 5.0, 6.0, 7.0, then 8.0
Date published by MongoDB software lifecycle schedules and production notes. We do not publish a lifecycle date we cannot source.
What actually stops on 29 February 2024
- Guaranteed patch releases for 4.4. Post-EOL releases are at MongoDB's discretion.
- Technical support for 4.4 under standard subscriptions.
- Compatibility testing with current drivers and tools.
What actually breaks in the upgrade
The AVX requirement
MongoDB 5.0 and later require the AVX instruction set on x86_64. Servers without AVX, and virtual machines that expose a generic CPU model such as kvm64, cannot run 5.0. The hardware or hypervisor configuration has to change before the upgrade can start.
Three upgrades to reach 7.0
4.4 to 5.0, 5.0 to 6.0 and 6.0 to 7.0 are separate upgrades, each followed by a featureCompatibilityVersion change.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Fix the platform, then upgrade | Expose AVX or move to newer hardware, then upgrade step by step. | Weeks to quarters | Hardware and engineering time | The destination. |
| Extended support on 4.4 | Committed fixes for self-managed 4.4 on your current hardware. | Days | Subscription | For estates where the hardware refresh is scheduled but not done. |
| Rely on discretionary releases | Take MongoDB's occasional post-EOL patches. | None | Zero | No SLA and no guarantee the next one will come. |
What OSSeva does for MongoDB 4.4
OSSeva patches this line
OSSeva provides committed security coverage for self-managed MongoDB 4.4, including on hardware without AVX.
MongoDB extended supportWhat your auditor will say
CC7.1. A database with no contracted source of security fixes is a finding.
MongoDB 4.4: common questions
When did MongoDB 4.4 reach end of life?
On 29 February 2024.
Why can't we upgrade MongoDB 4.4 to 5.0?
Usually because the CPU, or the CPU model the hypervisor exposes, lacks AVX. MongoDB 5.0 and later require it on x86_64.
Was MongoDB 4.4 patched for CVE-2025-14847?
Yes. MongoDB released 4.4.30 in December 2025 with the fix, despite 4.4 being past end of life. MongoDB 4.2 and earlier received no fix.
Still running MongoDB 4.4?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.