Apache Hop End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Apache Hop versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.0 | Oct 5, 2021 | Jan 24, 2022 | 1611 days past EOL | EOL |
| 1.1 | 1.1.0 | Jan 24, 2022 | Mar 8, 2022 | 1568 days past EOL | EOL |
| 1.2 | 1.2.0 | Mar 8, 2022 | Jun 2, 2022 | 1482 days past EOL | EOL |
| 2.0 | 2.0.0 | Jun 2, 2022 | Oct 14, 2022 | 1348 days past EOL | EOL |
| 2.1 | 2.1.0 | Oct 14, 2022 | Dec 7, 2022 | 1294 days past EOL | EOL |
| 2.2 | 2.2.0 | Dec 2, 2022 | Jan 27, 2023 | 1243 days past EOL | EOL |
| 2.3 | 2.3.0 | Jan 27, 2023 | Mar 27, 2023 | 1184 days past EOL | EOL |
| 2.4 | 2.4.0 | Mar 27, 2023 | Jun 8, 2023 | 1111 days past EOL | EOL |
| 2.5 | 2.5.0 | Jun 8, 2023 | Sep 12, 2023 | 1015 days past EOL | EOL |
| 2.6 | 2.6.0 | Sep 12, 2023 | Dec 1, 2023 | 935 days past EOL | EOL |
| 2.7 | 2.7.0 | Nov 17, 2023 | Mar 13, 2024 | 832 days past EOL | EOL |
| 2.8 | 2.8.0 | Feb 28, 2024 | May 20, 2024 | 764 days past EOL | EOL |
| 2.9 | 2.9.0 | May 20, 2024 | Oct 8, 2024 | 623 days past EOL | EOL |
| 2.10 | 2.10.0 | Oct 7, 2024 | Dec 4, 2024 | 566 days past EOL | EOL |
| 2.11 | 2.11.0 | Dec 4, 2024 | Feb 19, 2025 | 489 days past EOL | EOL |
| 2.12 | 2.12.0 | Feb 13, 2025 | Apr 22, 2025 | 427 days past EOL | EOL |
| 2.13 | 2.13.0 | Apr 15, 2025 | May 19, 2025 | 400 days past EOL | EOL |
| 2.14 | 2.14.0 | May 13, 2025 | Aug 20, 2025 | 307 days past EOL | EOL |
| 2.15 | 2.15.0 | Aug 12, 2025 | Nov 17, 2025 | 218 days past EOL | EOL |
| 2.16 | 2.16.0 | Nov 17, 2025 | Feb 6, 2026 | 137 days past EOL | EOL |
| 2.17 | 2.17.0 | Feb 6, 2026 | TBD | Supported | Active |
What does Apache Hop end of life mean for your organization?
When a version of Apache Hop 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: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Apache Hop 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Apache Hop versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →