Reactor Netty End of Life (EOL) Dates & Support Timeline

Reactor Netty lifecycle status — the real story

Reactor Netty, the non-blocking HTTP and TCP client and server built on Netty that underpins Spring WebFlux and Spring Cloud Gateway (reactor/reactor-netty on GitHub, Maven coordinates io.projectreactor.netty:reactor-netty-core); one line per minor version. Release days are the Maven Central publish dates from repo1.maven.org/maven2/io/projectreactor/netty/reactor-netty-core (read twice 2026-09-22, the directory listing and maven-metadata.xml agreeing on both ends of every line). 1.3 is the current line (1.3.0 on 2025-11-07; latest open-source release 1.3.7, 2026-08-20). 1.4 exists only as a milestone (1.4.0-M1) and is not listed.

End-of-life rule: support dates are the vendor's own, from Project Reactor's machine-readable support feed at projectreactor.io/support.json, library reactor-netty (read twice 2026-09-22, the reads agreed). That feed is the data behind the projectreactor.io/support page, which renders it client-side and shows nothing to a plain fetch, so the JSON is the primary vendor surface rather than a convenience copy. The mapping follows the one used for Spring Boot and Micrometer: eol is endOfOssSupport, the end of open-source support, and extendedSupport is endOfEnterpriseSupport, the end of commercial support from Broadcom. The feed's own metadata.lastUpdated field reads 2025-08-26 and is not maintained - the same document lists the 1.3 line with an initial release of 2025-11-07, after that date - so the field is ignored and the dates are checked against Maven Central instead.

On the 1.0 line the last open-source release on Maven Central (1.0.48, 2024-08-13) is dated more than a year after the stated open-source end of 2023-06-30; the vendor's stated date is what is served. The latest version shown for each line is the last open-source release on Maven Central. Releases made afterwards under commercial support are not published there and are not listed, but they do exist and are visible in the NIST CPE dictionary, which carries Broadcom Reactor Netty 1.0.53 and 1.2.19 titles against versions Maven Central does not have.

Commercial context: HeroDevs Never-Ending Support covers Reactor Netty 1.0.x (docs.herodevs.com/reactor-netty, NES for Reactor Netty 1.0, verified 2026-09-22). That is a commercial offering for the 1.0 line; it is not a project release. Broadcom's own enterprise support for 1.0 runs to 2029-06-30 per the vendor feed, and the 1.2 line carries the long commercial window to 2032-06-30.

Reactor Netty release and support pattern

Across the 4 release lines with a published release date, Reactor Netty has shipped a new line roughly every 2 years (median interval). A line typically stays in standard support for about 2.1 years from its release to its standard-support end date.

Of the 4 release lines tracked, 3 are past end of life and 1 is still within support. The newest line, 1.3, was released November 7, 2025. The next scheduled end of life is 1.3 on June 30, 2027 — 280 days from this build. Upstream also publishes an extended-support phase for 4 lines, shown in the table above.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does Reactor Netty end of life mean for your organization?

When a version of Reactor Netty reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL Reactor Netty should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when Reactor Netty reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Reactor Netty versions. This is a bridge, not a permanent solution — plan your migration in parallel.

Related Products