Apache Camel End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Apache Camel versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.0 | 3.0.1 | Nov 24, 2019 | Feb 20, 2020 | 2362 days past EOL | EOL |
| 2.25 LTS | 2.25.4 | Jan 19, 2020 | Jan 31, 2022 | 1651 days past EOL | EOL |
| 3.1 | 3.1.0 | Feb 20, 2020 | Apr 1, 2020 | 2321 days past EOL | EOL |
| 3.2 | 3.2.0 | Apr 1, 2020 | May 10, 2020 | 2282 days past EOL | EOL |
| 3.3 | 3.3.0 | May 10, 2020 | Jun 14, 2020 | 2247 days past EOL | EOL |
| 3.4 LTS | 3.4.6 | Jun 14, 2020 | Jun 30, 2021 | 1866 days past EOL | EOL |
| 3.5 | 3.5.0 | Aug 31, 2020 | Oct 16, 2020 | 2123 days past EOL | EOL |
| 3.6 | 3.6.0 | Oct 16, 2020 | Dec 11, 2020 | 2067 days past EOL | EOL |
| 3.7 LTS | 3.7.7 | Dec 11, 2020 | Dec 31, 2021 | 1682 days past EOL | EOL |
| 3.8 | 3.8.0 | Feb 9, 2021 | Mar 22, 2021 | 1966 days past EOL | EOL |
| 3.9 | 3.9.0 | Mar 22, 2021 | May 15, 2021 | 1912 days past EOL | EOL |
| 3.10 | 3.10.0 | May 15, 2021 | Jun 23, 2021 | 1873 days past EOL | EOL |
| 3.11 LTS | 3.11.7 | Jun 23, 2021 | Jun 30, 2022 | 1501 days past EOL | EOL |
| 3.12 | 3.12.0 | Sep 28, 2021 | Nov 8, 2021 | 1735 days past EOL | EOL |
| 3.13 | 3.13.0 | Nov 8, 2021 | Dec 12, 2021 | 1701 days past EOL | EOL |
| 3.14 LTS | 3.14.10 | Dec 12, 2021 | Dec 31, 2022 | 1317 days past EOL | EOL |
| 3.15 | 3.15.0 | Jan 31, 2022 | Mar 22, 2022 | 1601 days past EOL | EOL |
| 3.16 | 3.16.0 | Mar 22, 2022 | May 15, 2022 | 1547 days past EOL | EOL |
| 3.17 | 3.17.0 | May 15, 2022 | Jul 2, 2022 | 1499 days past EOL | EOL |
| 3.18 LTS | 3.18.8 | Jul 2, 2022 | Jul 31, 2023 | 1105 days past EOL | EOL |
| 3.19 | 3.19.0 | Sep 29, 2022 | Dec 16, 2022 | 1332 days past EOL | EOL |
| 3.20 LTS | 3.20.9 | Dec 16, 2022 | Dec 31, 2023 | 952 days past EOL | EOL |
| 3.21 LTS | 3.21.5 | Jun 23, 2023 | Jun 23, 2024 | 777 days past EOL | EOL |
| 4.0 LTS | 4.0.6 | Aug 10, 2023 | Aug 10, 2024 | 729 days past EOL | EOL |
| 4.1 | 4.1.0 | Oct 6, 2023 | Nov 15, 2023 | 998 days past EOL | EOL |
| 4.2 | 4.2.0 | Nov 10, 2023 | Dec 18, 2023 | 965 days past EOL | EOL |
| 4.3 | 4.3.0 | Dec 11, 2023 | Feb 12, 2024 | 909 days past EOL | EOL |
| 3.22 LTS | 3.22.4 | Dec 19, 2023 | Dec 26, 2024 | 591 days past EOL | EOL |
| 4.4 LTS | 4.4.5 | Feb 12, 2024 | Feb 12, 2025 | 543 days past EOL | EOL |
| 4.5 | 4.5.0 | Mar 23, 2024 | May 10, 2024 | 821 days past EOL | EOL |
| 4.6 | 4.6.0 | May 5, 2024 | Jul 13, 2024 | 757 days past EOL | EOL |
| 4.7 | 4.7.0 | Jul 9, 2024 | Sep 10, 2024 | 698 days past EOL | EOL |
| 4.8 LTS | 4.8.9 | Sep 10, 2024 | Sep 10, 2025 | 333 days past EOL | EOL |
| 4.9 | 4.9.0 | Nov 29, 2024 | Feb 11, 2025 | 544 days past EOL | EOL |
| 4.10 LTS | 4.10.9 | Feb 7, 2025 | Feb 11, 2026 | 179 days past EOL | EOL |
| 4.11 | 4.11.0 | Mar 29, 2025 | May 29, 2025 | 437 days past EOL | EOL |
| 4.12 | 4.12.0 | May 23, 2025 | Jul 4, 2025 | 401 days past EOL | EOL |
| 4.13 | 4.13.0 | Jul 4, 2025 | Aug 20, 2025 | 354 days past EOL | EOL |
| 4.14 LTS | 4.14.8 | Aug 15, 2025 | Aug 20, 2026 | 11 days remaining | Warning |
| 4.15 | 4.15.0 | Oct 7, 2025 | Nov 5, 2025 | 277 days past EOL | EOL |
| 4.16 | 4.16.0 | Nov 5, 2025 | Jan 12, 2026 | 209 days past EOL | EOL |
| 4.17 | 4.17.0 | Jan 12, 2026 | Feb 17, 2026 | 173 days past EOL | EOL |
| 4.18 LTS | 4.18.3 | Feb 17, 2026 | Feb 17, 2027 | 192 days remaining | Active |
| 4.19 | 4.19.0 | Apr 18, 2026 | Apr 23, 2026 | 108 days past EOL | EOL |
| 4.20 | 4.20.0 | Apr 23, 2026 | Jun 26, 2026 | 44 days past EOL | EOL |
| 4.21 | 4.21.0 | Jun 26, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/apache-camel)
What does Apache Camel end of life mean for your organization?
When a version of Apache Camel 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 Camel 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 Apache Camel 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.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Apache Camel versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Apache Camel has 43 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Apache Camel exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.