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 from endoflife.date, checked against the vendor's own lifecycle pages where we have read them (share on /accuracy). Updated at every deploy.
Apache Camel 4.23 is supported, with no end-of-life or end-of-support date announced yet. The next Apache Camel version to reach end of life is 4.18, on February 17, 2027. 45 of 48 tracked Apache Camel versions are past end of life; the most recent to reach it, 4.21, did so on August 11, 2026. The full Apache Camel lifecycle, with every version's release and end-of-support date, is in the table below.
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 | 2459 days past EOL | EOL |
| 2.25 LTS | 2.25.4 | Jan 19, 2020 | Jan 31, 2022 | 1748 days past EOL | EOL |
| 3.1 | 3.1.0 | Feb 20, 2020 | Apr 1, 2020 | 2418 days past EOL | EOL |
| 3.2 | 3.2.0 | Apr 1, 2020 | May 10, 2020 | 2379 days past EOL | EOL |
| 3.3 | 3.3.0 | May 10, 2020 | Jun 14, 2020 | 2344 days past EOL | EOL |
| 3.4 LTS | 3.4.6 | Jun 14, 2020 | Jun 30, 2021 | 1963 days past EOL | EOL |
| 3.5 | 3.5.0 | Aug 31, 2020 | Oct 16, 2020 | 2220 days past EOL | EOL |
| 3.6 | 3.6.0 | Oct 16, 2020 | Dec 11, 2020 | 2164 days past EOL | EOL |
| 3.7 LTS | 3.7.7 | Dec 11, 2020 | Dec 31, 2021 | 1779 days past EOL | EOL |
| 3.8 | 3.8.0 | Feb 9, 2021 | Mar 22, 2021 | 2063 days past EOL | EOL |
| 3.9 | 3.9.0 | Mar 22, 2021 | May 15, 2021 | 2009 days past EOL | EOL |
| 3.10 | 3.10.0 | May 15, 2021 | Jun 23, 2021 | 1970 days past EOL | EOL |
| 3.11 LTS | 3.11.7 | Jun 23, 2021 | Jun 30, 2022 | 1598 days past EOL | EOL |
| 3.12 | 3.12.0 | Sep 28, 2021 | Nov 8, 2021 | 1832 days past EOL | EOL |
| 3.13 | 3.13.0 | Nov 8, 2021 | Dec 12, 2021 | 1798 days past EOL | EOL |
| 3.14 LTS | 3.14.10 | Dec 12, 2021 | Dec 31, 2022 | 1414 days past EOL | EOL |
| 3.15 | 3.15.0 | Jan 31, 2022 | Mar 22, 2022 | 1698 days past EOL | EOL |
| 3.16 | 3.16.0 | Mar 22, 2022 | May 15, 2022 | 1644 days past EOL | EOL |
| 3.17 | 3.17.0 | May 15, 2022 | Jul 2, 2022 | 1596 days past EOL | EOL |
| 3.18 LTS | 3.18.8 | Jul 2, 2022 | Jul 31, 2023 | 1202 days past EOL | EOL |
| 3.19 | 3.19.0 | Sep 29, 2022 | Dec 16, 2022 | 1429 days past EOL | EOL |
| 3.20 LTS | 3.20.9 | Dec 16, 2022 | Dec 31, 2023 | 1049 days past EOL | EOL |
| 3.21 LTS | 3.21.5 | Jun 23, 2023 | Jun 23, 2024 | 874 days past EOL | EOL |
| 4.0 LTS | 4.0.6 | Aug 10, 2023 | Aug 10, 2024 | 826 days past EOL | EOL |
| 4.1 | 4.1.0 | Oct 6, 2023 | Nov 15, 2023 | 1095 days past EOL | EOL |
| 4.2 | 4.2.0 | Nov 10, 2023 | Dec 18, 2023 | 1062 days past EOL | EOL |
| 4.3 | 4.3.0 | Dec 11, 2023 | Feb 12, 2024 | 1006 days past EOL | EOL |
| 3.22 LTS | 3.22.4 | Dec 19, 2023 | Dec 26, 2024 | 688 days past EOL | EOL |
| 4.4 LTS | 4.4.5 | Feb 12, 2024 | Feb 12, 2025 | 640 days past EOL | EOL |
| 4.5 | 4.5.0 | Mar 23, 2024 | May 10, 2024 | 918 days past EOL | EOL |
| 4.6 | 4.6.0 | May 5, 2024 | Jul 13, 2024 | 854 days past EOL | EOL |
| 4.7 | 4.7.0 | Jul 9, 2024 | Sep 10, 2024 | 795 days past EOL | EOL |
| 4.8 LTS | 4.8.9 | Sep 10, 2024 | Sep 10, 2025 | 430 days past EOL | EOL |
| 4.9 | 4.9.0 | Nov 29, 2024 | Feb 11, 2025 | 641 days past EOL | EOL |
| 4.10 LTS | 4.10.9 | Feb 7, 2025 | Feb 11, 2026 | 276 days past EOL | EOL |
| 4.11 | 4.11.0 | Mar 29, 2025 | May 29, 2025 | 534 days past EOL | EOL |
| 4.12 | 4.12.0 | May 23, 2025 | Jul 4, 2025 | 498 days past EOL | EOL |
| 4.13 | 4.13.0 | Jul 4, 2025 | Aug 20, 2025 | 451 days past EOL | EOL |
| 4.14 LTS | 4.14.9 | Aug 15, 2025 | Aug 11, 2026 | 95 days past EOL | EOL |
| 4.15 | 4.15.0 | Oct 7, 2025 | Nov 5, 2025 | 374 days past EOL | EOL |
| 4.16 | 4.16.0 | Nov 5, 2025 | Jan 12, 2026 | 306 days past EOL | EOL |
| 4.17 | 4.17.0 | Jan 12, 2026 | Feb 17, 2026 | 270 days past EOL | EOL |
| 4.18 LTS | 4.18.5 | Feb 17, 2026 | Feb 17, 2027 | 95 days remaining | Warning |
| 4.19 | 4.19.0 | Apr 18, 2026 | Apr 23, 2026 | 205 days past EOL | EOL |
| 4.20 | 4.20.0 | Apr 23, 2026 | Jun 26, 2026 | 141 days past EOL | EOL |
| 4.21 | 4.21.0 | Jun 26, 2026 | Aug 11, 2026 | 95 days past EOL | EOL |
| 4.22 LTS | 4.22.2 | Aug 11, 2026 | Aug 11, 2027 | 270 days remaining | Active |
| 4.23 | 4.23.0 | Oct 15, 2026 | TBD | Supported | Active |
[](https://endoflife.ai/apache-camel)
Apache Camel release and support pattern
Across the 48 release lines with a published release date, Apache Camel has shipped a new line roughly every 2 months (median interval). A line typically stays supported for about 2 months from its release to its end-of-life date (measured on the 47 lines with both dates published). 16 of the 48 tracked lines are designated long-term support, which is where the longer windows sit.
Of the 48 release lines tracked, 45 are past end of life and 3 are still within support. The newest line, 4.23, was released October 15, 2026. The next scheduled end of life is 4.18 on February 17, 2027 — 94 days from this build. The longest-supported line currently published is 4.22, to August 11, 2027.
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 Apache Camel end of life mean for your organization?
When a version of Apache Camel reaches end of life, the vendor's standard security patches for that version stop. Vulnerabilities found after that date are still published on the National Vulnerability Database, exploit code often becomes public, and systems on that version stay exposed until they are upgraded or covered by extended support.
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 the vendor's policy provides no patch for the ended version. This is one of the most dangerous gaps 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.
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, check whether the vendor or a third party sells extended support with security patches for your Apache Camel version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
Apache Camel has 45 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Apache Camel is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."