Approaching77 days from today

RabbitMQ 4.3 end of life

RabbitMQ 4.3 leaves community support on 31 January 2027, about nine months after 4.3.0 shipped on 23 April 2026. Broadcom lists commercial support for 4.3 until 30 April 2028. The latest public release is 4.3.7. RabbitMQ 4.4.0 shipped on 20 October 2026, with community support to 31 July 2027 and commercial support to 31 October 2028, so 4.3 and 4.4 are the two lines in community support today. OSSeva ships patched 4.3 builds after the community date.

What now

Which vendors provide RabbitMQ 4.3 security patches after 31 January 2027?

Patched RabbitMQ 3.x Builds with SBOM and VEX Attestation
End of life
31 January 2027
Released
Apr 2026
Final release
4.3.7 (latest public release, 20 October 2026)
Successor
RabbitMQ 4.4 (released 20 October 2026, community support to 31 July 2027)

Date published by RabbitMQ release information. We do not publish a lifecycle date we cannot source.

Last reviewed

RabbitMQ versions: release and end-of-life dates

RabbitMQ release and end-of-life dates
VersionReleasedEnd of lifeStatus
RabbitMQ 4.3 (this page)23 Apr 202631 January 2027Approaching
RabbitMQ 4.228 Oct 202531 July 2026End of life
RabbitMQ 4.115 Apr 202531 January 2026End of life
RabbitMQ 4.018 Sept 202430 April 2025End of life
RabbitMQ 3.1322 Feb 202430 September 2024End of life
RabbitMQ 3.122 Jun 202329 February 2024End of life
RabbitMQ 3.1128 Sept 202230 June 2023End of life
RabbitMQ 3.81 Oct 201931 July 2022End of life

End-of-life dates are published by each project and checked against endoflife.date.

What actually stops on 31 January 2027

  • Public 4.3.x patch releases. After 31 January 2027, fixes on the line ship in Broadcom's commercial releases.
  • Public fixes for later advisories. In September 2026 NVD published 54 RabbitMQ server CVEs, including CVE-2026-67404 (9.2) and CVE-2026-67231 (9.1). 30 of them reach 4.3, and every 4.3 fix shipped in public releases up to 4.3.5, while the fixes for 3.13, 4.0 and 4.1 shipped only in commercial releases. After 31 January 2027, 4.3 moves to the commercial side of that line.
  • Community support for 4.3 after 31 January 2027. The newer 4.4 line is in community support until 31 July 2027, and moving to it means a feature release upgrade rather than a patch.

What actually breaks in the upgrade

Get to 4.3.7 first

Several of the September 2026 CVEs reach 4.3. CVE-2026-67409, a JWKS fetch that can wipe signing keys and block OAuth logins, and CVE-2026-67239, a stored XSS in the stream management UI, are fixed in 4.3.3. CVE-2026-67419, a topic-binding pattern that drives heavy CPU and memory use, is fixed in 4.3.5. Any 4.3 cluster below that should move to 4.3.7, the latest public release, before the community date.

Khepri is the only metadata store

4.3 removed Mnesia. Khepri is Raft-based, so a majority of nodes must be online for the cluster to be available. Partition handling settings in rabbitmq.conf are accepted but ignored, and the release notes recommend removing them.

Erlang 28 needs 4.3.6

RabbitMQ's compatibility matrix lists Erlang 27.0 as the minimum for 4.3 and marks Erlang 28 as fully supported from 4.3.6. Earlier 4.3 releases support Erlang 28 for new clusters only, because of a known issue with rolling upgrades from Erlang 27.

Your options, costed honestly

Including the ones that do not involve buying anything from us.

OptionWhat it isEffortCostOur view
OSSeva patched builds on 4.3Signed 4.3 builds with backported fixes for advisories published after the last public release.DaysSubscriptionKeeps the cluster patched from 1 December 2026 without waiting for 4.4.
Broadcom commercial supportBroadcom lists commercial support for 4.3 until 30 April 2028.ProcurementCommercial subscriptionA route to commercial patch releases, on Broadcom's licensing terms.
Upgrade to 4.4 when it shipsThe next feature release, with no published date yet.WeeksEngineering timeThe eventual destination. It cannot be planned against 30 November until a date exists.
Stay on public 4.3.xNo public fixes after the community date.NoneZero nowScanners will flag advisories fixed only in commercial releases, as they already do for 4.0 to 4.2.

What OSSeva does for RabbitMQ 4.3

OSSeva patches this line

OSSeva ships patched, signed RabbitMQ 4.3 builds, with backported fixes for the broker, the management and federation plugins and the Erlang runtime underneath. They continue after community support ends on 31 January 2027, on the Patch, Assure and Operate tiers, so the next advisory wave does not depend on a commercial release.

RabbitMQ extended support

What your auditor will say

PCI DSS v4 Requirement 6.3.3

Every system component in the cardholder data environment needs its applicable security patches. A runtime, framework or broker with no upstream fix supply needs a patched source or a documented compensating control.

SOC 2 CC7.1

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.

Compliance library RabbitMQ end of life dates for every version

Questions

RabbitMQ 4.3: common questions

Book a 15-minute call

When does RabbitMQ 4.3 reach end of life?

Community support ends on 31 January 2027. Broadcom lists commercial support for 4.3 until 30 April 2028. 4.3.0 was released on 23 April 2026.

Which RabbitMQ versions can upgrade to 4.3?

Only 4.2.x. RabbitMQ's upgrade guide says 3.13 users must upgrade to 4.2 first, and all stable feature flags, including khepri_db, must be enabled before the move.

What replaces RabbitMQ 4.3?

4.4.4, which shipped on 20 October 2026 and has community support to 31 July 2027. Moving from 4.3 to 4.4 is a feature release upgrade, so read the 4.4.0 breaking changes first.

Which Erlang version does RabbitMQ 4.3 need?

Erlang 27.0 or later. Erlang 28 is fully supported from 4.3.6, and earlier 4.3 releases support it for new clusters only.

Who patches RabbitMQ 4.3 after January 2027?

Broadcom, in commercial releases, and OSSeva, which ships patched, signed 4.3 builds on the Patch, Assure and Operate tiers.

Get a quote

Still running RabbitMQ 4.3?

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.

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

Prefer to talk or read more first?

Book a call