Back to blog

OSSeva Blog

Operations

End-of-life middleware patching: who covers Kafka, ZooKeeper, RabbitMQ and Redis

7 min read

Coverage for end-of-life middleware is thin and uneven. On the vendors' own pages on 15 November 2026, OpenLogic lists Kafka 3.8 and 3.9 as long-term-support builds, TuxCare lists Kafka 3.2.3 and 3.5.2, and HeroDevs lists Apache Kafka 3.1.x as a client library. None of the three lists a ZooKeeper, RabbitMQ or Redis build for end-of-life versions. OSSeva patches all four. OSSeva sells one of the options below; the method is at the end.

Running RabbitMQ in production? OSSeva patches and supports it, end-of-life versions included.

RabbitMQ extended support: what is covered

Which provider lists which product

Kafka is the only one of the four with more than one third-party provider of patched builds. For ZooKeeper, RabbitMQ and Redis, only OSSeva names builds on these pages. Each cell comes from that vendor's own page, read on 15 November 2026.

ProductHeroDevs (NES)TuxCare (ELS)OpenLogic (Perforce)OSSeva
Apache KafkaListed: Kafka 3.1.x, shown as the kafka-clients library, Java 11Listed: 3.2.3 and 3.5.2LTS: 3.8 to 30 November 2028, 3.9 to 31 March 2029Brokers 2.8 to 3.9
Apache ZooKeeperNot listedNot listedNot in the LTS list3.4, 3.6 and 3.7 patched; 3.5 as custom support
RabbitMQThe RabbitMQ Java Client only, not the brokerNot listedNot in the LTS list; not named on its database support page3.8 to 4.2, with the Erlang/OTP layer
RedisNot listedNot listedNot in the LTS list; Redis is named on its database support page6.2 and 7.0 on extended support; 7.2 and Valkey as current lines

Pages: herodevs.com/support and docs.herodevs.com/kafka/kafka-3-1, tuxcare.com/endless-lifecycle-support/applications-eol-support (modified 9 May 2026), openlogic.com/products/long-term-support and openlogic.com/solutions/databases. HeroDevs' catalogue page loads part of its list at a time, so a product missing here may appear on a later page of it. Nothing here covers a vendor's technical-support lists, which are separate from its patched-build lists, and a listing is not a statement that a specific CVE is fixed in a build.

What each provider says about patch timing

OpenLogic and TuxCare state patch windows for Kafka, and they cover different severities.

Runtimes have the same question. PHP extended support covers 7.4 to 8.3 and Python extended support covers 3.9 and 3.10.

ProviderWindow as stated on its own page
OpenLogicWithin 14 days of disclosure for critical CVEs (CVSS 9 and above), within 30 days for high severity (CVSS 7 and above); security patches for three years and bug fixes for one year on the Kafka long-term-support page
TuxCareIts Kafka post (11 May 2026) says high and critical issues (CVSS 7 and above) are addressed within 14 days of public disclosure, covering the broker and its dependencies such as Netty and Jackson. These are the vendor's own claims
HeroDevsNo Kafka-specific window on the Kafka documentation page read; its support page gives a general critical-fix target
OSSevaCritical within 48 hours, High within 7 days, for every technology

The windows are not like for like: each vendor counts from a different starting point and a different severity cut-off.

The upstream end dates these providers work from

The dates that matter are the upstream ones, because a provider's job starts where the project stops.

ProductWhat upstream saysSource and detail
RedisRedis 8.0 reaches end of life on 1 December 2026, Redis 6.2 on 1 April 2027 and Redis 7.2 and 7.4 on 1 December 2029. Extended releases get five years of security fixesRedis Open Source version management page. Redis 8.0 end of life and Redis EOL dates
RabbitMQ3.13 community support ended on 30 September 2024; Broadcom's commercial end date for 3.13 is 31 December 2029, which RabbitMQ lists as indicative. 4.3 community support ends on 31 January 2027RabbitMQ release information page. RabbitMQ EOL dates
KafkaKafka 3.9 is the last line that runs on ZooKeeper; Kafka 4.0 removed itKafka EOL dates and Kafka on ZooKeeper after 2026
ZooKeeperDates per line on the ZooKeeper chartZooKeeper EOL dates

The three product pages carry each version's date, and the Kafka and ZooKeeper dates are kept there rather than repeated here.

Which provider fits which situation

Match the provider to the layer that has gone end of life, not to the brand you already buy from.

  • Kafka 3.8 or 3.9 you intend to keep until a KRaft migration: OpenLogic's long-term-support builds and OSSeva both name those lines.
  • Kafka client libraries on 3.1: HeroDevs lists the kafka-clients artifact. If the broker is the exposure, it is not what the page lists.
  • Kafka 3.2 or 3.5 brokers: TuxCare lists both. OSSeva covers 2.8 to 3.9, which includes them.
  • ZooKeeper, RabbitMQ or Redis past end of life: on these pages only OSSeva names builds for them. Verify a quote against your exact version.
  • A mixed estate: coverage is per product, so one provider per layer is normal. Keep each component with a single provider so fixes are not delivered twice.

For a wider list, see open source extended support vendors, and the HeroDevs, TuxCare and OpenLogic comparison for the framework and runtime layers. Per-product provider lists: Kafka, ZooKeeper, RabbitMQ and Redis and Valkey.

How this was checked

Each vendor fact comes from that vendor's own page, opened on 15 November 2026 and listed above. A product was marked "not listed" only after reading the vendor's current list for it. Upstream dates come from each project's own page. OSSeva is one of the four options and its row uses only claims already published on this site; where another provider fits better, the table says so. Vendor catalogues change, so re-read the page before you buy.

Frequently asked questions

Who patches end-of-life Kafka?

Three third-party providers list Kafka on their own pages: OpenLogic (3.8 and 3.9 as LTS builds), TuxCare (3.2.3 and 3.5.2) and HeroDevs (3.1.x client library). OSSeva patches broker versions 2.8 to 3.9.

Can I get patched builds of end-of-life ZooKeeper?

On the vendor pages read on 15 November 2026, HeroDevs, TuxCare and OpenLogic list no ZooKeeper builds. OSSeva patches ZooKeeper 3.4, 3.6 and 3.7, with 3.5 as custom support.

Does anyone patch RabbitMQ 3.13 after its community support ended?

Broadcom, which owns RabbitMQ, lists a commercial end date of 31 December 2029 for 3.13, described as indicative. OSSeva patches RabbitMQ 3.8 to 4.2 including the Erlang/OTP layer beneath it.

Is Redis 6.2 end of life?

Redis lists 1 April 2027 as the end of life for 6.2, an extended release. After that date fixes come only from a third party. OSSeva covers 6.2 on extended support.

Tags

KafkaZooKeeperRabbitMQRedisEnd of LifeExtended SupportVendor Comparison

Get a quote

Ready to get your open source under control?

Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.

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

Prefer to talk or read more first?

Book a call