Back to all use cases
RabbitMQFinancial services

A broker with no supported runtime left

Consider a payments platform running several RabbitMQ 3.13 clusters with classic mirrored queues. Public 3.13 builds run only on Erlang/OTP 26, which reached end of life on 26 May 2026, and moving to RabbitMQ 4.x means redesigning every mirrored queue first.

Challenge

Two lifecycles have run out at once. RabbitMQ 3.13 left community support on 30 September 2024, and 3.13.7 was the last public release. Later 3.13 patch releases exist, but only for Broadcom's commercial customers: CVE-2025-50200 and CVE-2026-57213 were fixed on the 3.13 line in 3.13.8 and 3.13.14, which are not public. Underneath the broker, Erlang/OTP 26 stopped receiving patches on 26 May 2026, with 26.2.5.21 as its final release.

The two cannot be fixed separately. Public 3.13 builds support OTP 26.0 to 26.2.x only, so the runtime cannot move to OTP 27 while the broker stays on 3.13. The TLS, SSH and crypto code the broker relies on belongs to OTP, so a patched broker on an unpatched runtime is still an unpatched system.

The broker cannot move quickly either. RabbitMQ 4.0 removed classic queue mirroring, and the replacement, quorum queues, behaves differently on ordering, memory use and poison-message handling. That is application work for every team that publishes to or consumes from those queues, and in a PCI DSS environment each change needs its own evidence.

Environment

Several RabbitMQ 3.13 clusters on Erlang/OTP 26, with classic mirrored queues declared through ha-mode policies. The brokers carry payment events inside the cardholder data environment, so they fall under PCI DSS 4.0 Requirement 6.3.3 as system components.

The applications around them were built against mirrored-queue behaviour, and some were written by teams that no longer own them. Feature flags have been enabled release by release, and nobody has checked recently whether every stable flag is on.

Options

Upgrade to RabbitMQ 4.2 or 4.3 now. This is the right destination, but the quorum queue migration is the whole project, and RabbitMQ requires every stable feature flag to be enabled on the latest 3.13 patch before the jump. Community support for 4.3 runs to 31 January 2027, so the next upgrade follows soon after.

Buy commercial Tanzu RabbitMQ. Broadcom supports 3.13 for licence holders until 31 December 2029 and ships the non-public 3.13 patch releases. Tanzu RabbitMQ is licensed by CPU core count with minimum commitments, which fits large estates better than a handful of mid-size clusters.

Stay on 3.13.7 and OTP 26 without patches. It costs nothing today. It also leaves two layers without fixes inside an audited environment, and the management plugin is often more reachable than teams assume.

Take third-party extended support. A provider backports fixes to 3.13 and to OTP 26 so the broker and runtime stay patched while the queue migration runs at a safe pace. Ask any provider whether the Erlang layer is included.

Approach

OSSeva ships patched RabbitMQ 3.13 builds and patched Erlang/OTP 26 builds as a tested pair, signed with GPG and Sigstore and delivered as Helm charts, OCI images or Maven artifacts through your own repository manager. The Erlang/OTP compatibility matrix is published with each release, so the security team can see which runtime sits under which broker.

On OSSeva Assure, the same engagement plans the move to 4.x: a configuration and architecture audit of the existing clusters, a check that every stable feature flag is enabled, and a quorum queue design for each vhost, worked out with the application teams. The migration then runs one vhost at a time, with the patched 3.13 cluster carrying production until each set of queues has moved.

For the auditor, Assure includes the SOC 2, HIPAA and PCI attestation package and a pen-test validation summary. If the team wants operations covered as well, OSSeva Operate adds 24/7 monitoring on your own infrastructure and a 15-minute P1 incident response SLA.

What this delivers

A patched broker and a patched runtime for as long as the migration takes, on the version already in production. A 4.x migration planned one vhost at a time instead of rushed against an end-of-life date, and attestation documents that show the auditor how the gap is closed. OSSeva for RabbitMQ is priced per application cluster; book a discovery call for a quote.

Go deeper

Questions

Frequently asked questions

Book a 15-minute call

Does patching RabbitMQ 3.13 cover Erlang/OTP 26?

No. They are separate codebases with separate advisories, and the TLS, crypto and networking under the broker come from OTP. OSSeva patches both and ships them as a tested pair, so neither layer is left behind.

Can RabbitMQ 3.13 run on Erlang/OTP 27?

Not with public builds. Public RabbitMQ 3.13.x releases support Erlang/OTP 26 only, from 26.0 to 26.2.x. Moving to a newer runtime means moving the broker to 4.x as well.

Why not upgrade straight to RabbitMQ 4.x?

RabbitMQ 4.0 removed classic queue mirroring, so every mirrored queue has to become a quorum queue first. Quorum queues behave differently on ordering, memory use and poison-message handling, which makes the move application work rather than a broker setting. That is usually what takes quarters.

Are later RabbitMQ 3.13 patch releases public?

No. 3.13.7 was the last public release. Later 3.13 patch releases, such as 3.13.8 and 3.13.14, go only to Broadcom's commercial customers. Third-party extended support is the other source of fixes.

How does this help with PCI DSS?

PCI DSS 4.0 Requirement 6.3.3 expects security patches on in-scope system components, and a broker carrying payment events is one. OSSeva Assure includes a PCI attestation package that documents the patched builds running on each cluster.

See every EOL & CVE-patching use case

All use cases
Book a call