RabbitMQ 4.3 reaches the end of community support on 31 January 2027, per the project's release information page checked on 18 November 2026. RabbitMQ 4.4, community-supported to 31 July 2027, is the upgrade target, and a rolling upgrade from 4.3 is supported. This guide covers the dates, the Erlang requirement, the 4.4 breaking changes and your options after the date.
RabbitMQ 4.3 reaches the end of community support on 31 January 2027, 74 days after the 18 November 2026 check of the project's release information page. The supported move is the 4.4 series, which has community support to 31 July 2027. A 4.3 broker keeps running after the date, but the community stops shipping fixes for it, security fixes included.
4.3.0 was released on 23 April 2026, so the series gets about nine months of community support. This page covers 4.3 only. Dates for every RabbitMQ series, 3.x included, are on RabbitMQ end of life dates by version.
RabbitMQ 4.3 end of life date and the series around it
Series
Latest patch (18 Nov 2026)
First release
End of community support
End of commercial support (indicative)
4.4
4.4.1 (16 Nov 2026)
20 Oct 2026
31 Jul 2027
31 Oct 2028
4.3
4.3.8 (16 Nov 2026)
23 Apr 2026
31 Jan 2027
30 Apr 2028
4.2
4.2.9 (20 Jul 2026)
28 Oct 2025
31 Jul 2026 (ended)
30 Jun 2030
4.1
4.1.8 (22 Jan 2026)
15 Apr 2025
31 Jan 2026 (ended)
30 Apr 2027
The project marks commercial dates as indicative and points to the Broadcom support portal as authoritative. Each recent series has had about nine months of community support, so 4.4 ends on 31 July 2027 and moving to it, the lifecycle's latest series, buys roughly seven months, not years. Plan to upgrade on a cadence, or to buy support that runs past it.
What changes when RabbitMQ 4.3 reaches end of life
At end of life, security patches and bug fixes for new problems land in 4.4 and later but not in 4.3. Nothing breaks on 1 February. What grows is the list of known, unpatched issues on the broker, which is what a security auditor asks about. Check the RabbitMQ versions you run across every environment, because a forgotten staging cluster reaches end of life on the same day.
Erlang adds to it. 4.3.0 to 4.3.2 accept Erlang 26.2, which is itself out of support, and 4.4 needs Erlang 27.0 or newer, per the RabbitMQ Erlang version table. Erlang 28 is fully supported from 4.3.6 and Erlang 29 from 4.3.7.
How to upgrade RabbitMQ 4.3 to 4.4
A rolling upgrade from 4.3.x to 4.4.x is supported. In order:
Move to the latest 4.3 patch (4.3.8) and to Erlang 27 or newer first.
Enable every stable feature flag before you start. The upgrade guide warns the upgrade may fail otherwise.
Upgrade one node at a time and keep a majority of nodes online, because Khepri needs a quorum of nodes to serve.
Read the 4.4.0 breaking changes (below) against your configuration.
When every node is on 4.4, enable the feature flags the new version introduced.
Three 4.4.0 changes catch teams out:
OpenID Connect discovery is stricter. Non-HTTPS endpoints or an issuer mismatch now fail. Identity providers that do not comply may need auth_oauth2.discovery.verify_issuer or verify_https_endpoints set to false before the upgrade.
The password-hash endpoint changed.GET /api/auth/hash_password/{password} is replaced by a POST /api/auth/hash_password with a JSON body.
There is no way back. Nodes that start using the v2 classic queue message store cannot be downgraded to 4.3, and RabbitMQ does not officially support downgrades at all. Take a snapshot and rehearse on a copy.
Starting further back needs an extra hop, per the upgrade guide:
Where you start
Path to 4.4
4.3.x
Rolling upgrade to 4.4.x
4.2.x
Rolling upgrade to 4.3.x or 4.4.x
4.1.x or 4.0.x
Upgrade to 4.2.x first, then 4.3.x or 4.4.x
3.13.x
Upgrade to 4.2.x first, then 4.3.x or 4.4.x. A 3.13 cluster with Khepri enabled cannot be upgraded in place: use a blue-green migration to a new cluster
Upgrade to 4.4 before the date. The lowest-cost path, and the only one that keeps you on community patches. Schedule the next upgrade for before 31 July 2027.
Stay on 4.3 with commercial support. The project lists commercial support for 4.3 to 30 April 2028 (indicative), through Broadcom's Tanzu RabbitMQ.
Stay on 4.3 with extended support. AceMQ keeps a broker patched on the build you run after community support ends, with 24/7 support from a named senior engineer. See RabbitMQ extended support and CVE patching.
AceMQ also runs a RabbitMQ health check that reviews version posture, feature flags and upgrade readiness before a move. Response targets start from 15 minutes, by plan, and quote requests are answered within 1 hour.
Community support for RabbitMQ 4.3 ends on 31 January 2027, per the project's release information page. The same page lists commercial support for 4.3 to 30 April 2028 and marks that date as indicative.
What is the latest RabbitMQ version?
RabbitMQ 4.4.1, released on 16 November 2026, is the latest patch of the 4.4 series. The latest 4.3 patch is 4.3.8, also released on 16 November 2026.
Can I upgrade RabbitMQ 4.3 to 4.4 without downtime?
A rolling upgrade from 4.3.x to 4.4.x is supported. Enable all stable feature flags first, upgrade one node at a time and keep a majority of nodes online.
Does RabbitMQ 4.3 need Erlang 27?
4.3.3 and later need Erlang 27.0 or newer; 4.3.0 to 4.3.2 accept 26.2. Erlang 28 is fully supported from 4.3.6 and Erlang 29 from 4.3.7. RabbitMQ 4.4 needs 27.0 or newer.
Can I keep running RabbitMQ 4.3 after 31 January 2027?
Yes, the broker keeps working, but the community stops fixing it. Either upgrade to 4.4, buy commercial support, or use extended support that patches the 4.3 build you run.
Can I roll back from RabbitMQ 4.4 to 4.3?
Not officially. RabbitMQ says downgrades are not tested, and nodes that use the 4.4 v2 classic queue message store cannot go back to 4.3. Keep a snapshot and rehearse the upgrade first.
Whether you're troubleshooting a production incident, planning a migration, or want a second opinion on your architecture — our team is ready. No pitch, just answers.