Apache Camel End of Life (EOL) Dates and End of Support (EOS) Dates

Latest Release: 4.23.0

Apache Camel end of life (EOL) and end of support (EOS) dates: 45 Apache Camel versions have reached EOL, including Apache Camel 4.21 (EOL date: Aug 11, 2026) — no longer receiving security updates or patches. Apache Camel 4.18 (LTS) reaches its End of Support date on Feb 17, 2027 — plan your upgrade path now. Apache Camel 4.23.0 is the current supported release — 2 versions in active support. Also see Apache ActiveMQ Classic end of support life for related end-of-life information.

Apache Camel end of life dates timeline — release schedule chart of the 8 most recent Apache Camel versions, mapping security support windows against their EOL dates
Apache Camel end of life dates and end of support (EOS) dates shown as a release schedule — support windows for the 8 most recent Apache Camel releases of 48 total. Each bar runs from the release date to the end of security support, with the dashed line marking today. Exact Apache Camel EOL, EOS and EOSL dates for every version are listed in the tables below.

Currently Supported Apache Camel Releases - Active EOS/EOSL Support (2)

Release Supported Java Versions Released Bug and Security Fixes Latest LTS
4.23 17, 21, 25 (1 month and 6 days ago) Active 4.23.0 (1 month and 1 week ago) -
4.22 (LTS) 17, 21, 25 (3 months ago) (in 8 months) 4.22.2 (1 month and 4 days ago) LTS

Apache Camel Releases Nearing End of Life - Support Ending Soon (1)

Important: The following Apache Camel releases will reach End of Life (EOL) within 6 months. Plan your migration to a supported release to ensure continued security updates and support.
Release Supported Java Versions Released Bug and Security Fixes Latest LTS
4.18 (LTS) 17, 21 (9 months ago) (in 2 months) 4.18.5 (1 month and 2 weeks ago) LTS

Apache Camel End of Life (EOL) Releases - No Longer Supported (45)

Release Supported Java Versions Released Bug and Security Fixes Latest LTS
4.21 17, 21, 25 (4 months ago) (3 months ago) 4.21.0 (4 months ago) -
4.20 17, 21, 25 (6 months ago) (4 months ago) 4.20.0 (6 months ago) -
4.19 17, 21 (7 months ago) (6 months ago) 4.19.0 (7 months ago) -
4.17 17, 21 (10 months ago) (9 months ago) 4.17.0 (10 months ago) -
4.16 17, 21 (1 year ago) (10 months ago) 4.16.0 (1 year ago) -
4.15 17, 21 (1 year and 1 month ago) (1 year ago) 4.15.0 (1 year and 1 month ago) -
4.14 (LTS) 17, 21 (1 year and 3 months ago) (3 months ago) 4.14.9 (3 months ago) LTS
4.13 17, 21 (1 year and 4 months ago) (1 year and 3 months ago) 4.13.0 (1 year and 4 months ago) -
4.12 17, 21 (1 year and 5 months ago) (1 year and 4 months ago) 4.12.0 (1 year and 5 months ago) -
4.11 17, 21 (1 year and 7 months ago) (1 year and 5 months ago) 4.11.0 (1 year and 7 months ago) -
4.10 (LTS) 17, 21 (1 year and 9 months ago) (9 months ago) 4.10.9 (9 months ago) LTS
4.9 17, 21 (1 year and 11 months ago) (1 year and 9 months ago) 4.9.0 (1 year and 11 months ago) -
4.8 (LTS) 17, 21 (2 years and 2 months ago) (1 year and 2 months ago) 4.8.9 (1 year and 2 months ago) LTS
4.7 17, 21 (2 years and 4 months ago) (2 years and 2 months ago) 4.7.0 (2 years and 4 months ago) -
4.6 17, 21 (2 years and 6 months ago) (2 years and 4 months ago) 4.6.0 (2 years and 6 months ago) -
4.5 17, 21 (2 years and 7 months ago) (2 years and 6 months ago) 4.5.0 (2 years and 7 months ago) -
4.4 (LTS) 17, 21 (2 years and 9 months ago) (1 year and 9 months ago) 4.4.5 (1 year and 10 months ago) LTS
3.22 (LTS) 11, 17 (2 years and 11 months ago) (1 year and 10 months ago) 3.22.4 (1 year and 8 months ago) LTS
4.3 17, 21 (2 years and 11 months ago) (2 years and 9 months ago) 4.3.0 (2 years and 11 months ago) -
4.2 17, 21 (3 years ago) (2 years and 11 months ago) 4.2.0 (3 years ago) -
4.1 17 (3 years and 1 month ago) (3 years ago) 4.1.0 (3 years and 1 month ago) -
4.0 (LTS) 17 (3 years and 3 months ago) (2 years and 3 months ago) 4.0.6 (2 years and 3 months ago) LTS
3.21 (LTS) 11, 17 (3 years and 4 months ago) (2 years and 4 months ago) 3.21.5 (2 years and 5 months ago) LTS
3.20 (LTS) 11, 17 (3 years and 11 months ago) (2 years and 10 months ago) 3.20.9 (2 years and 11 months ago) LTS
3.19 11, 17 (4 years and 1 month ago) (3 years and 11 months ago) 3.19.0 (4 years and 1 month ago) -
3.18 (LTS) 11, 17 (4 years and 4 months ago) (3 years and 3 months ago) 3.18.8 (3 years and 5 months ago) LTS
3.17 11, 17 (4 years and 6 months ago) (4 years and 4 months ago) 3.17.0 (4 years and 6 months ago) -
3.16 11 (4 years and 7 months ago) (4 years and 6 months ago) 3.16.0 (4 years and 7 months ago) -
3.15 11 (4 years and 9 months ago) (4 years and 7 months ago) 3.15.0 (4 years and 9 months ago) -
3.14 (LTS) 8, 11 (4 years and 11 months ago) (3 years and 10 months ago) 3.14.10 (3 years ago) LTS
3.13 8, 11 (5 years ago) (4 years and 11 months ago) 3.13.0 (5 years ago) -
3.12 8, 11 (5 years and 1 month ago) (5 years ago) 3.12.0 (5 years and 1 month ago) -
3.11 (LTS) 8, 11 (5 years and 4 months ago) (4 years and 4 months ago) 3.11.7 (4 years and 6 months ago) LTS
3.10 8, 11 (5 years and 6 months ago) (5 years and 4 months ago) 3.10.0 (5 years and 6 months ago) -
3.9 8, 11 (5 years and 7 months ago) (5 years and 6 months ago) 3.9.0 (5 years and 7 months ago) -
3.8 8, 11 (5 years and 9 months ago) (5 years and 7 months ago) 3.8.0 (5 years and 9 months ago) -
3.7 (LTS) 8, 11 (5 years and 11 months ago) (4 years and 10 months ago) 3.7.7 (4 years and 11 months ago) LTS
3.6 8, 11 (6 years and 1 month ago) (5 years and 11 months ago) 3.6.0 (6 years and 1 month ago) -
3.5 8, 11 (6 years and 2 months ago) (6 years and 1 month ago) 3.5.0 (6 years and 2 months ago) -
3.4 (LTS) 8, 11 (6 years and 5 months ago) (5 years and 4 months ago) 3.4.6 (5 years and 5 months ago) LTS
3.3 8, 11 (6 years and 6 months ago) (6 years and 5 months ago) 3.3.0 (6 years and 6 months ago) -
3.2 8, 11 (6 years and 7 months ago) (6 years and 6 months ago) 3.2.0 (6 years and 7 months ago) -
3.1 8, 11 (6 years and 9 months ago) (6 years and 7 months ago) 3.1.0 (6 years and 9 months ago) -
2.25 (LTS) 8 (6 years and 10 months ago) (4 years and 9 months ago) 2.25.4 (5 years and 5 months ago) LTS
3.0 8, 11 (6 years and 11 months ago) (6 years and 9 months ago) 3.0.1 (6 years and 10 months ago) -

If you run integration routes in production, Apache Camel end of life dates decide when your fixes stop. Camel is an open source framework and message-oriented middleware that implements Enterprise Integration Patterns in Java. As of October 2026, only the 4.22 and 4.18 LTS lines plus the latest 4.23 release still receive support. Below you can see what has reached EOL and how to plan your next move for this open-source project.

Apache Camel End of Life: Which Releases Are Still Supported

The latest release, 4.23, shipped on 15 October 2026 and supports Java 17, 21 and 25. It gets bug and security fixes only while it stays current. The same routing and mediation engine, rule-based routing and domain-specific language power every supported line, with over 300 components, data formats and APIs on the same runtime. Camel's public API stays stable inside a major line, which makes patch upgrades cheap. Before choosing a version, check the project on GitHub or its download page for the supported list.

Supported Releases and Java Support

Java support narrows as versions age, so match your JDK to the line you run. Each major release passes through milestone and release candidate builds, a minor release follows every few months, and a patch release carries fixes into an LTS line. You pull them through Maven or a Spring Boot starter, and endoflife.date publishes the same schedule as an RSS feed with CPE and PURL identifiers for scanners. Community statistics show almost 500 million downloads in 2025, so many teams face the same support cutoffs.

Release lineTypeJava supportSupport ends
4.23Latest release17, 21, 25When superseded
4.22LTS release17, 21, 2511 Aug 2027
4.18LTS release17, 2117 Feb 2027
4.14LTS release17, 21Ended 11 Aug 2026

Apache Camel 3 - End of Life: What Ended and When

Apache Camel 3 reached its end of life when 3.22, the last Camel 3 LTS release, ended on 26 December 2024. The project's roadmap gave a year of warning in a 2023 post titled "last year of support" and confirmed the end-of-life in December 2024. Legacy 3.x users get no more patches, so every affected version in that line stays exposed to newly found flaws, and the 3.21 LTS line already ended on 23 June 2024. Camel 3 was reaching end of life for a reason: the team supports the 4.x LTS lines instead.

Last Year of Support and the LTS Release Cycle

Two LTS releases ship each year, and each one is supported for one year. Support means fixes for security problems and important or critical bugs. Non-LTS versions get none once they are replaced. Each new LTS release then gets maintenance builds, as the recent archive entries show.

VersionDateDescription
4.22.22026-10-22New LTS release 4.22.2
4.18.52026-10-11New LTS release 4.18.5
4.22.12026-09-17New LTS release 4.22.1
4.18.42026-08-17New LTS release 4.18.4
4.14.92026-08-16New LTS release 4.14.9
4.22.02026-08-11New LTS release 4.22.0
4.14.82026-07-04New LTS release 4.14.8
4.18.32026-07-03New LTS release 4.18.3
4.14.72026-04-24New LTS release 4.14.7
4.18.22026-04-22New LTS release 4.18.2
4.14.62026-04-18New LTS release 4.14.6
4.18.12026-03-27New LTS release 4.18.1

Semantic Versioning and Bug and Security Fixes

Camel follows Semantic Versioning, so a patch release such as 4.22.2 holds only bug and security fixes and is safe to adopt. Developers should stay on the newest patch of their LTS line.

Risks of Running an End-of-Life Apache Camel Version

Once a Camel 3.x or retired 4.x line leaves support, newly reported flaws get no upstream fix, and every unpatched flaw in an end-of-life version becomes a permanent risk for your enterprise. Auditors flag it as a compliance gap, and upgrading late costs more. The real security exposure comes from what the project can no longer fix, so mitigations such as network isolation only reduce the danger.

CVE and Vulnerabilities Left Unpatched

CVE-2020-11971 is a critical-severity remote code execution flaw: JMX integration did not secure the binding process, so a malicious actor could replace a trusted remote object with their own. Affected versions run from 3.0.0 to 3.1.0, plus 2.25.0 and 2.24.x. OWASP ranks this class among the most damaging, and CVSS rates it Critical. Check NVD and vendor security advisories for each vulnerability that applies to your version; a patch available upstream helps only if you can reach a supported line.

Transitive Dependencies and Patches

On an unsupported Camel line, the libraries its components pull in through Maven get no upstream bump, so one vulnerable library deep in the dependency tree forces a rebuild of everything above it. Patching means each fix needs a backport, tests in your CI/CD pipeline and a fresh release across the whole stack.

Endless Lifecycle Support and Other EOL Options

When you cannot upgrade yet, third parties sell post-EOL security support for Apache Camel versions past their EOL date. TuxCare's endless lifecycle support offers SLA-backed patches and 24/7 help, including fixes in transitive dependencies. HeroDevs ships Never-Ending Support (NES) with a fix for CVE-2020-11971. OSSeva lists Apache Camel 3 and 4 support providers, and Red Hat documents its own supported configurations for its Camel build. Compare each on coverage and SLA.

Camel K and Camel Quarkus: Release Lines Reaching End of Life

Camel K and Camel Quarkus follow their own numbering and support status, separate from the core LTS table above. Quarkus 3.40.0 landed on 28 September 2026 and Camel K 2.11.0 on 7 September 2026. Kamelets, Karaf, the Kafka Connector and upgrade recipes are listed separately in the archive, and Camel K Runtime has not had a release since March 2025, so treat that line as no longer moving with the core, and check each line's own roadmap before relying on it.

Download and Upgrade Plan for an EOL Apache Camel Release

Running end of life Apache Camel versions is fixable in a few steps:

  1. Read your current version from the build file and compare it with the supported table.
  2. Download the newest patch of the 4.22 LTS line, or 4.18 if you are still on Java 17 and 21 only.
  3. Run the upgrade recipes and test your routes before moving to production.

EOL dates of related software products