Reactor Netty 1.2 · Version Status

Reactor Netty 1.2 End of Life Date

Reactor Netty 1.2 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

Reactor Netty 1.2 is past end of life. Standard support ended June 30, 2026. Patches continue until June 30, 2032 only under Tanzu Spring commercial support, a paid programme — if you are not covered by it, this version is unpatched today.
EOL Date
Jun 30, 2026
84 days past EOL
Latest Release
1.2.18
Standard release
Release Date
Nov 12, 2024
Reactor Netty 1.2 series
Extended Support
Jun 30, 2032
Tanzu Spring commercial support · paid
Lifecycle detail

Reactor Netty 1.2 was released on November 12, 2024 and support ended on June 30, 2026 — a supported lifespan of 1 year and 8 months, shorter than the 2 years and 8 months median for Reactor Netty releases. Its most recent release is 1.2.18, published June 8, 2026. Standard support ended 3 months ago. Security fixes now come only through extended support, published to June 30, 2032; without it this version is unpatched.

← Reactor Netty 1.1 All Reactor Netty versions Reactor Netty 1.3 →
35 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
25/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
Recommended upgrade path
Reactor Netty 1.3
Latest release: 1.3.7 · EOL: Jun 30, 2027
View full Reactor Netty timeline →
Extended Support
Extended Reactor Netty 1.2 support is available

Commercial vendors offer security patches beyond EOL. Right now that coverage spans Reactor Netty 1.x. Compare your options.

Compare Options →
All Reactor Netty Versions
VersionLatestEOL DateStatus
1.0 1.0.48 Jun 30, 2023 EOL
1.1 1.1.31 Jun 30, 2025 EOL
1.2 1.2.18 Jun 30, 2026 EOL
1.3 1.3.7 Jun 30, 2027 Active

What does Reactor Netty 1.2 end of life mean?

When Reactor Netty 1.2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Reactor Netty 1.2 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Reactor Netty 1.3 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Reactor Netty 1.2 reach end of life?
Reactor Netty 1.2 reached end of life on June 30, 2026. This version is no longer receiving security patches.
Is Reactor Netty 1.2 still supported?
No. Reactor Netty 1.2 reached end of life on June 30, 2026 and is no longer receiving security patches.
What should I upgrade to from Reactor Netty 1.2?
The recommended upgrade from Reactor Netty 1.2 is Reactor Netty 1.3 — the latest actively supported version. Check the Reactor Netty full timeline for all supported versions.
What are the security risks of running Reactor Netty 1.2 past EOL?
When Reactor Netty 1.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Reactor Netty should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →