End of life

MongoDB 4.4 end of life

MongoDB 4.4 end of life was 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.

What now

Which vendors provide MongoDB 4.4 security patches now that support has ended?

MongoDB 4.4 to 6.0 After End of Life: Patched Builds

Only your email is required · An engineer replies within 1 business day · No commitment

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. Dates checked on endoflife.date on 20 October 2026.

Last reviewed

MongoDB versions: release and end-of-life dates

MongoDB release and end-of-life dates
VersionReleasedEnd of lifeStatus
MongoDB 8.02 Oct 202431 October 2029Supported
MongoDB 7.01 Aug 202331 August 2027Approaching
MongoDB 6.05 Jul 202231 July 2025End of life
MongoDB 5.08 Jul 202131 October 2024End of life
MongoDB 4.4 (this page)25 Jul 202029 February 2024End of life

End-of-life dates are published by each project and checked against endoflife.date.

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.

CVEs published since MongoDB 4.4 ended

These are the CVEs in OSSeva's CVE directory that name MongoDB 4.4 and were published after 29 February 2024. MongoDB has shipped a fix on 4.4 for each so far, up to 4.4.31; its support policy does not promise the next.

Counts from the directory as of 20 October 2026 (MongoDB 4.4: 3 since 29 Feb 2024, 3 scored 7.0 or higher).

MongoDB CVEs published after each line ended, from the OSSeva CVE directory

LineCVECVSSPublishedIssueFixed upstream in
MongoDB 4.4CVE-2026-119338.812 Jun 2026MongoDB Server: use after free in server-side JavaScript BSON-to-array conversion4.4.31
MongoDB 4.4CVE-2025-148477.519 Dec 2025MongoDB Server: unauthenticated heap memory read through zlib-compressed message headers (MongoBleed)4.4.30
MongoDB 4.4CVE-2024-13519.87 Mar 2024MongoDB Server: peer certificate validation skipped when TLS is enabled without a CA file4.4.29

The directory lists MongoDB CVEs with a CVSS score of 7.0 or higher, matched at NVD to the product, so it is a subset of every MongoDB advisory. A CVE is listed when its affected range names the line and it was published after the line's end date. Fixed-in versions are from MongoDB's advisories. MongoDB's support policy does not oblige it to release fixes for ended lines.

MongoDB 4.4 on hardware without AVX

A host without AVX cannot start mongod from 5.0, so 4.4 is the newest line it can run. MongoDB's production notes give the minimum x86_64 microarchitectures: for Intel, a Haswell or later Core processor or a Tiger Lake or later Celeron or Pentium; for AMD, Bulldozer or later. Run grep -c avx /proc/cpuinfo on the machine that runs mongod: 0 means the CPU the operating system sees has no AVX, which in a virtual machine can be a setting rather than the hardware.

The solution page maps each CPU family to the newest MongoDB line it starts and shows how patched 4.4 builds cover hosts that cannot move yet.

Your options, costed honestly

Including the ones that do not involve buying anything from us.

OptionWhat it isEffortCostOur view
Fix the platform, then upgradeExpose AVX or move to newer hardware, then upgrade step by step.Scales with host count, replica sets, drivers and test coverageHardware and engineering timeThe destination.
Extended support on 4.4Committed fixes for self-managed 4.4 on your current hardware: Critical 48 hours, High 7 days.Starts from your current versionSubscription, priced per clusterFor estates where the hardware refresh is scheduled but not done.
Rely on discretionary releasesTake MongoDB's occasional post-EOL patches.NoneZeroNo 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 support

What your auditor will say

SOC 2

CC7.1. A database with no contracted source of security fixes is a finding.

Compliance library MongoDB end of life dates for every version

Questions

MongoDB 4.4: common questions

Book a 15-minute call

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.

Get a quote

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.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call