RabbitMQ 3.9 end of life
RabbitMQ 3.9 reached the end of general support on 31 January 2023. Its last release, 3.9.29, was published on 9 March 2023 and needs Erlang 24.3 or newer, with support for Erlang 25. Neither Erlang line is patched upstream any more. The RabbitMQ project does not patch 3.9, and OSSeva ships patched, signed 3.9 builds for clusters that cannot move yet.
What now
Which vendors provide RabbitMQ 3.9 security patches now that support has ended?
Patched RabbitMQ 3.x Builds with SBOM and VEX Attestation- End of life
- 31 January 2023
- Released
- Jul 2021
- Final release
- 3.9.29 (9 March 2023)
- Successor
- RabbitMQ 4.3, via 3.10 to 3.13, or a Blue/Green move
Date published by RabbitMQ 3.9.29 release notes. We do not publish a lifecycle date we cannot source. Dates and versions checked against the RabbitMQ release notes, upgrade guide and endoflife.date on 19 November 2026.
Last reviewed
RabbitMQ versions: release and end-of-life dates
| Version | Released | End of life | Status |
|---|---|---|---|
| RabbitMQ 4.3 | 23 Apr 2026 | 31 January 2027 | Approaching |
| RabbitMQ 4.2 | 28 Oct 2025 | 31 July 2026 | End of life |
| RabbitMQ 4.1 | 15 Apr 2025 | 31 January 2026 | End of life |
| RabbitMQ 4.0 | 18 Sept 2024 | 30 April 2025 | End of life |
| RabbitMQ 3.13 | 22 Feb 2024 | 30 September 2024 | End of life |
| RabbitMQ 3.12 | 2 Jun 2023 | 29 February 2024 | End of life |
| RabbitMQ 3.11 | 28 Sept 2022 | 30 June 2023 | End of life |
| RabbitMQ 3.9 (this page) | 23 Jul 2021 | 31 January 2023 | End of life |
| RabbitMQ 3.8 | 1 Oct 2019 | 31 July 2022 | End of life |
End-of-life dates are published by each project and checked against endoflife.date.
What actually stops on 31 January 2023
- Public patch releases on the 3.9.x line. 3.9.29, published on 9 March 2023, was the last.
- Fixes for later advisories. Anything reported after 31 January 2023 that reaches 3.9 stays open, because no release after 3.9.29 exists.
- Erlang compatibility updates. 3.9.29 runs on Erlang 24.3 and 25 only, and Erlang 26 support starts with RabbitMQ 3.12.0.
- Extended support. endoflife.date records extended support for 3.9 ending on 31 July 2023.
What actually breaks in the upgrade
Four rolling upgrades to reach 3.13, and a fifth to leave 3.x
RabbitMQ's upgrade guide lists 3.9.x to 3.10.x as the only rolling upgrade from this series. The chain then runs 3.10 to 3.11, 3.11.18 or later to 3.12, 3.12 to 3.13, and 3.13 to 4.0, 4.1 or 4.2. The guide requires every stable feature flag to be enabled before each rolling upgrade, or the upgrade may fail. A Blue/Green deployment, which migrates to a fresh cluster instead of upgrading nodes, replaces the chain with one move. RabbitMQ upgrade guide.
Erlang 24.3 is a floor, not a patch level
3.9.29 will not start on Erlang older than 24.3, and it supports Erlang 25. Both lines are out of upstream support: OTP 24 ended on 10 May 2024 and OTP 25 on 17 May 2025. The runtime then changes during the chain, because Erlang 26 arrives with RabbitMQ 3.12.0.
Classic mirrored queues end at 4.0
3.9 still supports mirrored classic queues. RabbitMQ 4.0 removed classic queue mirroring after three years of deprecation, so a 3.9 cluster that depends on it has to move those queues to quorum queues or streams before it can run 4.x. Streams were new in 3.9, which makes them available as a target on this series already. Mirrored queues to quorum queues.
What RabbitMQ 3.9 introduced, and why it shapes the upgrade
RabbitMQ 3.9.0 was released on 23 July 2021. Its release notes name three headline changes: streams, a persistent, replicated queue type that models an append-only log and lets consumers read repeatedly without removing messages, reached through a new binary protocol as well as AMQP 0-9-1; support for Erlang 24, which the notes describe as 20% to 50% higher throughput on many workloads the core team and community tested; and structured JSON logging, alongside per-protocol and per-queue-type message rates in Prometheus metrics. A 3.9 cluster that adopted streams has stream data and stream-protocol clients that go through every hop below, so rehearse them in staging first.
3.9.0 required Erlang 23.2 and recommended Erlang 24. The floor rose over the life of the series: 3.9.29 requires Erlang 24.3 or later and states that nodes fail to start on older releases. That makes 3.9 a two-runtime series, Erlang 24 and 25, and a minor-version floor says nothing about patch level. CVE-2022-37026, a client authentication bypass in Erlang's SSL, TLS and DTLS code scored 9.8 under CVSS 3.1, affects OTP 24 before 24.3.4.2 and OTP 25 before 25.0.2. The 3.9.29 minimum of 24.3 does not exclude those builds, so a node that installed Erlang 24.3 in 2022 and never updated it can still carry the flaw.
The upgrade is a chain, not a jump. From 3.9 the supported rolling path is 3.10, then 3.11, then 3.12 (from 3.11.18 or later), then 3.13, and only 3.13.x can move to 4.0, 4.1 or 4.2. That is four rolling upgrades to reach 3.13, a fifth to reach 4.x, and an Erlang change at 3.12. At each hop, list the feature flags first and enable every stable flag that is off, because the upgrade guide says a rolling upgrade can fail otherwise.
The queues need planning before the hops do. Mirrored classic queues, which 3.9 supports, are gone in 4.0, and the migration to quorum queues changes ordering, memory use and poison-message handling. Either plan that migration alongside the chain, or build a 4.x cluster next to the old one and move publishers and consumers across.
What vulnerability scanners report on RabbitMQ 3.9
No release after 3.9.29 exists, so any advisory that reaches 3.9 stays open on this series. Scanners do not always agree with RabbitMQ on which advisories reach it. NVD's record for CVE-2023-46118 (CVSS 4.9) lists RabbitMQ versions before 3.11.24 with no lower bound, so a scanner fed from NVD can flag 3.9.29. The GitHub advisory for the same CVE (GHSA-w6cq-9cf4-gqpg) starts the affected range at 3.11.0, which leaves 3.9 out. When a scan flags a 3.9 node, check the vendor advisory before you treat the cluster as exposed, and record the reason if you accept the finding.
The Erlang runtime is a different matter: CVE-2022-37026, described above, does apply to unpatched OTP 24 and 25 builds, and 3.9.29 accepts both. Patch level matters as much as the RabbitMQ version.
Sources
The 3.9.0 release date, headline features and Erlang 23.2 requirement come from the RabbitMQ 3.9.0 release notes. The 31 January 2023 end of general support, the 3.9.29 date, the Erlang 24.3 floor and Erlang 25 support come from the 3.9.29 release notes. The upgrade paths and the feature-flag rule come from the RabbitMQ upgrade guide, the Erlang 26 start from the Erlang compatibility page, and the removal of mirrored classic queues from the 4.0 release notes. Extended-support dates are as endoflife.date records them.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Upgrade to RabbitMQ 4.3 | Rolling upgrades through 3.10, 3.11, 3.12 and 3.13, then 4.x, with the queue migration on the way. | Months | Engineering time | The destination. Settle the mirrored queue migration first, because it decides the date. |
| Blue/Green to a new 4.x cluster | Build a current cluster and move publishers and consumers across. | Weeks | Parallel infrastructure plus engineering time | Replaces the chain of five rolling upgrades with one migration, at the cost of running two clusters for a while. |
| OSSeva patched builds on 3.9 | Signed 3.9 builds with backported CVE fixes for the broker and its Erlang 24 or 25 runtime. | Days | Priced per cluster | Keeps the cluster patched and auditable while the upgrade runs on your timeline. |
| Stay unpatched | No public fixes since March 2023, on an Erlang runtime that is itself unsupported. | None | Zero now | A broker sits in the path of every integration it serves. A poor place to carry open advisories. |
What OSSeva does for RabbitMQ 3.9
OSSeva patches this line
OSSeva ships patched, signed RabbitMQ 3.9 builds on the Patch, Assure and Operate tiers, with CVE backports for the broker and the Erlang 24 and 25 runtimes beneath it, delivered through your own repository manager. Pricing is per cluster. OSSeva engineers also plan the chain to 3.13 and run the mirrored to quorum queue migration when the cluster is ready to move.
RabbitMQ extended supportWhat your auditor will say
Every system component in the cardholder data environment needs its applicable security patches. A broker with no upstream fix supply needs a patched source or a documented compensating control.
Auditors ask for evidence that production systems receive security fixes. A version past end of life fails that test unless another supplier ships the fixes and can show which CVEs they close.
When did RabbitMQ 3.9 reach end of life?
General support ended on 31 January 2023, according to the 3.9.29 release notes. 3.9.0 was released on 23 July 2021 and the last release, 3.9.29, on 9 March 2023. endoflife.date records extended support ending on 31 July 2023.
What is the last RabbitMQ 3.9 release?
3.9.29, published on 9 March 2023. It requires Erlang 24.3 or later and supports Erlang 25. Nothing has been released on the 3.9 line since.
Which Erlang version does RabbitMQ 3.9 need?
3.9.0 required Erlang 23.2 or later. 3.9.29 requires Erlang 24.3 or later and supports Erlang 25, and nodes fail to start on older Erlang releases. Erlang 26 support starts with RabbitMQ 3.12.0.
Can I upgrade RabbitMQ 3.9 straight to 4.x?
Not with a rolling upgrade. The supported chain is 3.9 to 3.10, 3.10 to 3.11, 3.11.18 or later to 3.12, 3.12 to 3.13, and 3.13 to 4.x, with all stable feature flags enabled before each move. A Blue/Green deployment to a new 4.x cluster avoids the chain.
Does RabbitMQ 3.9 have known vulnerabilities?
Anything reported after support ended stays unfixed in 3.9, since 3.9.29 is the last release. Scanners can also flag 3.9 for CVE-2023-46118, because NVD lists every version before 3.11.24, while RabbitMQ's GitHub advisory starts at 3.11.0. The Erlang runtime beneath 3.9 has its own advisories, such as CVE-2022-37026, and OTP 24 and 25 are out of support.
Can I get security patches for RabbitMQ 3.9?
Yes, from a third-party provider. OSSeva ships patched, signed 3.9 builds that cover the broker and the Erlang runtime, priced per cluster. See RabbitMQ 3 extended support.
Get a quote
Still running RabbitMQ 3.9?
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.
Prefer to talk or read more first?