// MongoDB end of life: 4.4, 5.0 and 6.0

MongoDB after end of life: keep 4.4, 5.0 or 6.0 running safely

MongoDB 4.4, 5.0 and 6.0 are past end of life, and MongoDB's support policy does not oblige it to ship fixes for them. OSSeva provides committed security patches for self-managed Community Server on those lines, including 4.4 on hardware without AVX, so the hardware or the upgrade can take the time it needs. Enter your work email and the version you run, and an engineer replies within 1 business day.

Covered
Self-managed Community Server 4.4, 5.0 and 6.0 (4.2 too), replica sets and sharded clusters, with or without AVX
Critical CVEs (CVSS 9.0 or higher)
Patched within 48 hours
High-severity CVEs
Patched within 7 days
Support hours
Assure includes 24/7 reactive support; Operate adds a 15-minute P1 response
MongoDB end of life
4.4: 29 Feb 2024. 5.0: 31 Oct 2024. 6.0: 31 Jul 2025 (checked on endoflife.date, 20 October 2026)
MongoDB 4.45.06.04.2Community ServerReplica setsSharded clusters

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

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

MongoDB versions past end of life, and why teams are stuck on them

MongoDB 4.4, 5.0 and 6.0 reached end of life on the dates below (checked on endoflife.date on 20 October 2026). Databases keep running; what stops is a promised supply of fixes. A MongoDB upgrade is rarely one step, and sometimes the hardware blocks it.

The AVX trap

On x86_64, MongoDB 5.0 and later require the AVX instruction set. Older servers, and virtual machines using a generic CPU model such as kvm64, do not expose AVX, so mongod typically stops at start with an illegal instruction error. Those estates cannot leave 4.4 until the platform changes.

One major version at a time

MongoDB upgrades pass through every major release, raising featureCompatibilityVersion at each step. Going from 4.4 to 7.0 is three upgrades of every replica set and shard, each with its own driver checks, and how long that takes depends on the number of replica sets and shards, the drivers in use and how well the application is tested.

Drivers and applications move too

Newer server versions drop support for old wire protocol versions and old drivers. MongoDB also states that drivers released more than three years after a server version's end of life are not compatible with that version, so applications pinned to an old driver have to be updated before the server can move.

The dates that matter

  1. 2023-04-30

    MongoDB 4.2 end of life.

  2. 2024-02-29

    MongoDB 4.4 end of life. 4.4 is the last line that runs on x86_64 CPUs without AVX.

  3. 2024-10-31

    MongoDB 5.0 end of life.

  4. 2025-07-31

    MongoDB 6.0 end of life.

  5. 2025-12-29

    CVE-2025-14847, an unauthenticated read of heap memory through compressed message headers, is added to CISA's Known Exploited Vulnerabilities catalogue. Fixed in 4.4.30, 5.0.32 and 6.0.27; the directory lists no fix for 4.2.

  6. 2026-06

    MongoDB publishes 4.4.31, 5.0.34 and 6.0.29, the newest releases on the three ended lines, with the fix for CVE-2026-11933. Nothing in MongoDB's policy promises a next one.

  7. 2027-08-31

    MongoDB 7.0 end of life. 8.0 follows on 31 October 2029 and 9.0 on 31 October 2031.

What OSSeva delivers

1

Patched MongoDB builds

Committed security fixes for self-managed MongoDB 4.4, 5.0 and 6.0, and 4.2, including the 4.4 line that runs without AVX, delivered as signed packages and images. Critical CVEs (CVSS 9.0 or higher) are patched within 48 hours and High within 7 days.

OSSeva PatchNon-AVXSigned
2

Exposure and hardware review

Authentication, TLS and network exposure checks for every mongod and mongos, because an internet-reachable database is the most common MongoDB incident, plus an AVX check of every host and hypervisor CPU model and a driver audit. Assure includes 24/7 reactive support.

OSSeva Assure24/7 reactiveAVX check
3

Upgrade run

Each featureCompatibilityVersion step planned and rehearsed, then run replica set by replica set, with a 15-minute P1 response while it happens.

OSSeva Operate15-minute P1FCV steps

The AVX problem on older hardware

MongoDB 5.0 and later need the AVX instruction set on x86_64. MongoDB's production notes now list the minimum x86_64 microarchitectures it supports: for Intel, a Haswell or later Core processor, or a Tiger Lake or later Celeron or Pentium; for AMD, Bulldozer or later. A CPU below that line is where 4.4 stays the newest line that starts.

What counts is the CPU the operating system sees. A virtual machine on a modern host can still present a generic CPU model with no AVX, so the first check is on the machine that runs mongod.

Which MongoDB line each kind of CPU can run (MongoDB production notes, checked 20 October 2026)

Where mongod runsAVXNewest MongoDB line it startsWhat to do
Intel Xeon or Core before Sandy Bridge (Nehalem and Westmere, such as Xeon 5500 and 5600 series)No4.4Patched 4.4 builds until the hardware is replaced.
AMD before Bulldozer (K10 generation Opteron and Phenom II)No4.4Patched 4.4 builds until the hardware is replaced.
Intel Sandy Bridge and Ivy BridgeYesBelow MongoDB's published Haswell minimum; test before relying on 5.0 or laterRehearse on a copy first, or treat as 4.4 hardware.
Intel Celeron and Pentium before Tiger Lake, and most Atom-class serversGenerally no4.4Patched 4.4 builds until the hardware is replaced.
Virtual machine with a generic CPU model (qemu64, kvm64, or a low cluster baseline)Hidden from the guest4.4 until the CPU model changesPass the host CPU through or choose a Haswell-or-later model, then 5.0 and later can start.
ARM64 below ARMv8.2-A, such as a Raspberry Pi 4Not applicable4.4Not supported from 5.0 on.
Intel Haswell or later Core, Tiger Lake or later Celeron and Pentium, AMD Bulldozer or laterYesEvery current lineUpgrade one major version at a time.

To check a host, run grep -c avx /proc/cpuinfo on the machine that runs mongod; 0 means the CPU the operating system sees has no AVX. Source: the x86_64 and ARM64 sections of MongoDB's production notes. Rows for older Intel and AMD parts are OSSeva's mapping of those minimums.

CVEs affecting MongoDB 4.4 to 6.0

These are the CVEs in OSSeva's CVE directory that affect each line and were published after it reached end of life. MongoDB has shipped a fix on the ended lines for every one of them so far, but nothing in its support policy promises the next, and for 4.2 the directory lists no fix for CVE-2025-14847, which CISA lists as exploited.

Counts from the directory as of 20 October 2026 (MongoDB 4.4: 3 since 29 Feb 2024, 3 scored 7.0 or higher; MongoDB 5.0: 5 since 31 Oct 2024, 5 scored 7.0 or higher; MongoDB 6.0: 3 since 31 Jul 2025, 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
MongoDB 5.0CVE-2026-119338.812 Jun 2026MongoDB Server: use after free in server-side JavaScript BSON-to-array conversion5.0.34
MongoDB 5.0CVE-2026-80538.813 May 2026MongoDB Server: out-of-bounds write in time-series collections with duplicate field names5.0.33
MongoDB 5.0CVE-2025-148477.519 Dec 2025MongoDB Server: unauthenticated heap memory read through zlib-compressed message headers (MongoBleed)5.0.32
MongoDB 5.0CVE-2025-30859.81 Apr 2025MongoDB Server: intermediate certificates not checked for revocation on Linux5.0.31
MongoDB 5.0CVE-2024-109218.114 Nov 2024MongoDB Server: malformed BSON leads to buffer over-reads or crashes5.0.30
MongoDB 6.0CVE-2026-119338.812 Jun 2026MongoDB Server: use after free in server-side JavaScript BSON-to-array conversion6.0.29
MongoDB 6.0CVE-2026-80538.813 May 2026MongoDB Server: out-of-bounds write in time-series collections with duplicate field names6.0.28
MongoDB 6.0CVE-2025-148477.519 Dec 2025MongoDB Server: unauthenticated heap memory read through zlib-compressed message headers (MongoBleed)6.0.27

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.

What a patched build adds when MongoDB still ships fixes

Today the fixes exist upstream, so a patched build is not about missing code. It is about a supply you can write into a control: a named response time by severity, signed builds you install from your own repository, a record of which CVEs each build closes, and cover for the day MongoDB stops, which for 4.2 has already happened.

The record is the part auditors ask for. OSSeva Assure produces an SBOM and remediation record per build, so a scanner finding on a patched 4.4 host can be answered with the build that closes it.

Upgrade, move to Atlas, or run patched builds: how to choose

OptionWhat you getTrade-off
Upgrade to 7.0, 8.0 or 9.0A supported release: 7.0 to 31 Aug 2027, 8.0 to 31 Oct 2029, 9.0 to 31 Oct 2031 (endoflife.date, 20 October 2026)One major version at a time, AVX-capable hardware and driver updates. Scope follows the number of replica sets and shards, the drivers in use and the test coverage.
MongoDB ELS Add-OnUp to two years of support for one minor version after EOLAn add-on to Enterprise Advanced, not available for Community Server.
Move to MongoDB AtlasA managed, upgraded service run by MongoDBA migration and a new cost model; not an option for every data residency or network requirement.
OSSeva patched buildsPatched self-managed 4.4, 5.0 and 6.0 with a committed fix window: Critical 48 hours, High 7 daysA subscription, priced per cluster, while you stay on the line. It buys time for the upgrade and does not replace it.
Rely on MongoDB's discretionary releasesThe post-EOL releases MongoDB has shipped so far, latest June 2026Nothing commits to the next one, and 4.2 got no fix for CVE-2025-14847. Not evidence an auditor accepts.
Stay unpatchedNothingExposed MongoDB is one of the most scanned targets on the internet.

End-of-life dates checked on endoflife.date on 20 October 2026, matching MongoDB's lifecycle schedules. AVX and CPU requirements from MongoDB's production notes. KEV date from CISA's catalogue. CVE rows from the OSSeva CVE directory.

Questions

Frequently asked questions

Book a 15-minute call

Is MongoDB 4.4 end of life?

Yes. MongoDB 4.4 reached end of life on 29 February 2024. MongoDB has published later 4.4 releases, the newest 4.4.31 in June 2026, but its support policy carries no obligation to do so. 4.4 is also the last line that runs on x86_64 CPUs without AVX.

When are MongoDB 5.0 and 6.0 end of life?

MongoDB 5.0 reached end of life on 31 October 2024 and 6.0 on 31 July 2025. 7.0 follows on 31 August 2027, 8.0 on 31 October 2029 and 9.0 on 31 October 2031. Dates checked on endoflife.date on 20 October 2026.

Why does MongoDB 5.0 say it requires a CPU with AVX support?

MongoDB 5.0 and later require the AVX instruction set on x86_64. If the processor, or the CPU model the hypervisor exposes, lacks AVX, mongod stops on start, and the official Docker image warns that MongoDB 5.0+ requires a CPU with AVX support. Run it on AVX-capable hardware, pass AVX through from the hypervisor, or stay on 4.4 with patched builds.

Does MongoDB still patch 4.4, 5.0 and 6.0?

Sometimes. MongoDB has published post-EOL releases, most recently 4.4.31, 5.0.34 and 6.0.29 in June 2026, but its support policy carries no obligation to do so, and 4.2 got no fix for CVE-2025-14847. For a committed response time, MongoDB sells an Extended Lifecycle Support add-on to Enterprise Advanced customers; OSSeva provides committed coverage for Community Server.

Which CVEs affect MongoDB 4.4, 5.0 and 6.0?

The table above lists them from OSSeva's CVE directory: 4.4 has 3 since 29 Feb 2024, 5.0 has 5 since 31 Oct 2024, 6.0 has 3 since 31 Jul 2025. Every one has a fix on its line today. CVE-2025-14847 is the one CISA lists as exploited.

Can MongoDB be self-hosted?

Yes. MongoDB Community Server and Enterprise Advanced both run on your own servers, virtual machines or Kubernetes, and that is the estate OSSeva supports. Self-hosting means you own patching, so a line past end of life needs a supply of fixes you can rely on.

Do you support MongoDB Atlas?

No. Atlas is managed and patched by MongoDB. We support self-managed Community Server.

What about the SSPL?

MongoDB Community Server is under the Server Side Public License. Running it for your own applications is the common case and is what we support; offering MongoDB as a service to third parties carries SSPL obligations regardless of who supports it.

Get a quote

Keep MongoDB 4.4, 5.0 or 6.0 patched while the hardware catches up.

Send your work email and the version you run. An engineer replies within 1 business day; support is priced per cluster.

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

Prefer to talk or read more first?

Book a call