RabbitMQ End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all RabbitMQ versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
RabbitMQ 4.3 is supported, with no end-of-life or end-of-support date announced yet. 17 of 18 tracked RabbitMQ versions are past end of life; the most recent to reach it, 4.2, did so on July 31, 2026. The full RabbitMQ 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 ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 3.0 | 3.0.4 | Nov 19, 2012 | Nov 30, 2013 | — | 4680 days past EOL | EOL |
| 3.1 | 3.1.5 | May 1, 2013 | Apr 30, 2014 | — | 4529 days past EOL | EOL |
| 3.2 | 3.2.4 | Oct 23, 2013 | Oct 31, 2014 | — | 4345 days past EOL | EOL |
| 3.3 | 3.3.5 | Apr 2, 2014 | Mar 31, 2015 | — | 4194 days past EOL | EOL |
| 3.4 | 3.4.4 | Oct 21, 2014 | Oct 31, 2015 | — | 3980 days past EOL | EOL |
| 3.5 | 3.5.8 | Mar 11, 2015 | Oct 31, 2016 | — | 3614 days past EOL | EOL |
| 3.6 | 3.6.16 | Dec 22, 2015 | May 31, 2018 | — | 3037 days past EOL | EOL |
| 3.7 | 3.7.28 | Nov 28, 2017 | Sep 30, 2020 | — | 2184 days past EOL | EOL |
| 3.8 | 3.8.35 | Oct 1, 2019 | Jul 31, 2022 | — | 1515 days past EOL | EOL |
| 3.9 | 3.9.29 | Jul 23, 2021 | Jan 31, 2023 | Jul 31, 2023 VMware Extended Commercial Support (ended) |
1331 days past EOL | EOL |
| 3.10 | 3.10.25 | May 3, 2022 | Sep 28, 2022 | Dec 31, 2023 VMware Extended Commercial Support (ended) |
1456 days past EOL | EOL |
| 3.11 | 3.11.28 | Sep 26, 2022 | Jun 1, 2023 | Jun 29, 2024 VMware Extended Commercial Support (ended) |
1210 days past EOL | EOL |
| 3.12 | 3.12.14 | Jun 1, 2023 | Feb 21, 2024 | Jun 29, 2025 VMware Extended Commercial Support (ended) |
945 days past EOL | EOL |
| 3.13 | 3.13.7 | Feb 22, 2024 | Sep 17, 2024 | Dec 30, 2027 VMware Extended Commercial Support |
736 days past EOL | EOL |
| 4.0 | 4.0.9 | Sep 18, 2024 | Apr 15, 2025 | Sep 29, 2027 VMware Extended Commercial Support |
526 days past EOL | EOL |
| 4.1 | 4.1.8 | Apr 15, 2025 | Jan 30, 2026 | Apr 29, 2028 VMware Extended Commercial Support |
236 days past EOL | EOL |
| 4.2 | 4.2.9 | Oct 27, 2025 | Jul 31, 2026 | Jun 30, 2030 VMware Extended Commercial Support |
54 days past EOL | EOL |
| 4.3 | 4.3.6 | Apr 23, 2026 | TBD | — | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/rabbitmq)
RabbitMQ release and support pattern
Across the 18 release lines with a published release date, RabbitMQ has shipped a new line roughly every 7 months (median interval). A line typically stays in standard support for about 1 year from its release to its standard-support end date (measured on the 17 lines with both dates published).
Of the 18 release lines tracked, 17 are past end of life and 1 is still within support. The newest line, 4.3, was released April 23, 2026. No end-of-life date is currently published for the 1 supported line. Upstream also publishes an extended-support phase for 17 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 RabbitMQ end of life mean for your organization?
When a version of RabbitMQ 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 RabbitMQ 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 RabbitMQ 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.
| Option | Best when | Watch 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 RabbitMQ versions. This is a bridge, not a permanent solution — plan your migration in parallel.
RabbitMQ has 17 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 RabbitMQ 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."