Mautic · Lifecycle Status

Mautic End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Mautic versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Mautic 7.2 reaches end of life on September 30, 2026. Plan your migration now — 7 days remaining.

Mautic 7.2 is supported until September 30, 2026, its end-of-support date. It is also the next Mautic version to reach end of life. 16 of 18 tracked Mautic versions are past end of life; the most recent to reach it, 7.1, did so on June 30, 2026. The full Mautic lifecycle, with every version's release and end-of-support date, is in the table below.

Running an EOL version? Get matched with support options — free ↓
📅 Get reminded before Mautic 7.2 reaches EOL on September 30, 2026 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
Latest Active
— series
Next EOL
7.2
Sep 30, 2026
Active Versions
0
of 18 total
EOL Versions
16
no longer patched
35 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
25/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →
CPE Identifier
cpe:2.3:a:acquia:mautic
The Common Platform Enumeration name vulnerability scanners and CVE records use for Mautic. Verified against the NIST CPE dictionary. Machine-readable for all products: cpe-map.json
Package URL (purl)
pkg:github/mautic/mautic/
The package URL identifier SBOM tools emit for Mautic, so a CycloneDX or SPDX component resolves to this page by exact identifier rather than by name. Machine-readable for all products: purl-map.json; whole-SBOM checks: POST /v1/sbom or the Stack Scanner.
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20202021202220232024202520262.152.163.03.13.23.34.04.14.24.34.45.05.15.26.07.07.17.2TODAY
16 versions of Mautic are past end of life — security patches have stopped. Get matched with support →
All Versions
VersionLatest ReleaseRelease DateEOL DateExtended SupportDaysStatus
2.15 2.15.3 Oct 8, 2019 Oct 8, 2019 2542 days past EOL EOL
2.16 2.16.5 Feb 13, 2020 Dec 15, 2020 2108 days past EOL EOL
3.0 3.0.2 Jun 15, 2020 Dec 15, 2021 1743 days past EOL EOL
3.1 3.1.2 Aug 24, 2020 Nov 30, 2020 2123 days past EOL EOL
3.2 3.3.2 Nov 30, 2020 Feb 22, 2021 2039 days past EOL EOL
3.3 3.3.5 Feb 22, 2021 May 24, 2021 1948 days past EOL EOL
4.0 4.0.2 May 24, 2021 Nov 29, 2021 1759 days past EOL EOL
4.1 4.1.2 Nov 29, 2021 Feb 28, 2022 1668 days past EOL EOL
4.2 4.2.2 Feb 28, 2022 May 23, 2022 1584 days past EOL EOL
4.3 4.3.1 May 23, 2022 Jun 27, 2022 1549 days past EOL EOL
4.4 4.4.13 Jun 27, 2022 Dec 31, 2024 Dec 31, 2026
Extended support
631 days past EOL EOL
5.0 5.0.4 Jan 9, 2024 Jun 13, 2024 832 days past EOL EOL
5.1 5.1.1 Jun 13, 2024 Dec 2, 2024 660 days past EOL EOL
5.2 LTS 5.2.11 Dec 2, 2024 Jun 30, 2026 Jun 30, 2028
Extended support
85 days past EOL EOL
6.0 LTS 6.0.9 Mar 25, 2025 Sep 30, 2026 Sep 30, 2027
Extended support
7 days remaining Warning
7.0 7.0.2 Jan 20, 2026 Apr 14, 2026 162 days past EOL EOL
7.1 7.1.3 Apr 14, 2026 Jun 30, 2026 85 days past EOL EOL
7.2 7.2.0 Sep 2, 2026 Sep 30, 2026 7 days remaining Warning
EOL date vs extended support. The EOL Date column is the end of standard, included support. Extended support terms vary by vendor. Check whether the programme covers you before relying on these dates. 2 versions of Mautic are past the standard EOL date but still inside the extended support window.
Mautic EOL status badge Live EOL badge for your README — updates automatically at every build. [![Mautic EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Fmautic.json)](https://endoflife.ai/mautic)

Mautic release and support pattern

Across the 18 release lines with a published release date, Mautic has shipped a new line roughly every 4 months (median interval). A line typically stays in standard support for about 3 months from its release to its standard-support end date (measured on the 17 lines with both dates published). 2 of the 18 tracked lines are designated long-term support, which is where the longer windows sit.

Of the 18 release lines tracked, 16 are past end of life and 2 are still within support. The newest line, 7.2, was released September 2, 2026. The next scheduled end of life is 7.2 on September 30, 2026 — 7 days from this build. The longest-supported line currently published is 6.0, to September 30, 2026. Upstream also publishes an extended-support phase for 3 lines, shown in the table above.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does Mautic end of life mean for your organization?

When a version of Mautic reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL Mautic should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when Mautic reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

OptionBest whenWatch out for
Move to a supported version The system will outlive the current version's support window and you can schedule the work Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits
Replace the component The project is unmaintained, or a better-supported alternative exists The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem
Buy extended support Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application A bridge, not a destination — every year purchased is a year the migration still has to happen
Document accepted risk The system is isolated, short-lived, or scheduled for retirement Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Mautic versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Get Mautic Support Options

Mautic has 16 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Mautic is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."

Free · No obligation · Independent — we track the dates, vendors don't pay for placement · Dates verified against vendor sources
Frequently Asked Questions
What is the end-of-life date for Mautic?
The next Mautic version reaching EOL is 7.2 on September 30, 2026. See the full table above for all version EOL dates.
When is the Mautic support end date?
The next Mautic support end date is September 30, 2026, when version 7.2 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of Mautic?
The latest active version of Mautic is . Always verify against the table above as support windows can change.
What happens when Mautic reaches end of life?
When Mautic reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor patch path — a growing attack surface that a CVE-based scan does not show. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give the date in advance.
How do I check if I'm running an EOL version of Mautic?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Mautic versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Upstream dataset: endoflife.date API · endoflife.date · Generated at build time · How we source data →
Mautic end-of-life status badge