Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 · Version Status
Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 End of Life Date
Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (access.redhat.com); the source of each date is on the product page.
✓
Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 is actively supported. EOL date: November 30, 2027.
📅 Get reminded before Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 reaches EOL on November 30, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Nov 30, 2027
407 days remaining
Latest Release
—
Standard release
Release Date
May 4, 2026
Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 series
Where these dates come from
End of lifeNov 30, 2027Vendor's own page, checked by a person · access.redhat.com · checked Oct 19, 2026high · 2 sources agree End of active supportMay 31, 2027Vendor's own page, checked by a person · access.redhat.com · checked Oct 19, 2026high · 2 sources agree ReleaseMay 4, 2026Vendor's own page, checked by a person · access.redhat.com · checked Oct 19, 2026high · 2 sources agree
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 was released on May 4, 2026 and support is scheduled to end on November 30, 2027 — a planned supported lifespan of 1 year and 7 months, longer than the 5 months median for Streams for Apache Kafka (Red Hat AMQ Streams) releases.
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 →
All Streams for Apache Kafka (Red Hat AMQ Streams) Versions
| Version | Latest | EOL Date | Status |
| 2.9 |
— |
Oct 31, 2026 |
Warning |
| 1.8 |
— |
Jan 31, 2022 |
EOL |
| → 3.2 |
— |
Nov 30, 2027 |
Active |
| 3.1 |
— |
May 4, 2026 |
EOL |
| 3.0 |
— |
Dec 16, 2025 |
EOL |
What does Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 end of life mean?
When Streams for Apache Kafka (Red Hat AMQ Streams) 3.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 Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 reach end of life?
Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 reaches end of life on November 30, 2027. That is 407 days remaining.
Is Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 still supported?
Yes, Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 is currently supported. The EOL date is November 30, 2027.
What should I upgrade to from Streams for Apache Kafka (Red Hat AMQ Streams) 3.2?
What are the security risks of running Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 past EOL?
When Streams for Apache Kafka (Red Hat AMQ Streams) 3.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 Streams for Apache Kafka (Red Hat AMQ Streams) should migrate immediately or implement compensating controls.