Apache Camel 3 end of life
Apache Camel 3 is end of life. The final release on the 3.x line was 3.22.4 on 9 March 2025, and Camel's download page now lists only 4.x LTS releases as supported. Camel 3 deployments receive no further security fixes, and the move to Camel 4 requires the javax-to-jakarta namespace migration.
What now
Which vendors provide Apache Camel 3 security patches now that support has ended?
Apache Camel extended support- End of life
- 9 March 2025 (final release)
- Released
- Nov 2019
- Final release
- 3.22.4
- Successor
- Camel 4 LTS
Date published by Apache Camel releases and download pages. We do not publish a lifecycle date we cannot source.
Last reviewed
Apache Camel versions: release and end-of-life dates
| Version | Released | End of life | Status |
|---|---|---|---|
| Apache Camel 4.18 LTS | 17 Feb 2026 | February 2027 | Approaching |
| Apache Camel 3 (this page) | 28 Nov 2019 | 9 March 2025 (final release) | End of life |
End-of-life dates are published by each project and checked against endoflife.date.
What actually stops on 9 March 2025
- Security and bug fixes for every 3.x line, including the 3.14, 3.20 and 3.22 LTS releases
- Component-level fixes for the marshalling and transport components where Camel advisories concentrate
What actually breaks in the upgrade
Camel 3 to 4 is a namespace migration, not a version bump
Camel 4 moved to the Jakarta EE namespaces and raised the Java baseline to 17. Every javax import across routes, custom processors, type converters and tests has to change. For an estate with hundreds of routes that is a coordinated change with a full integration regression behind it.
Spring Boot moves with it
Camel Spring Boot is released in lockstep with Camel core and pins a compatible Spring Boot line, so Camel 3 to 4 generally drags Spring Boot 2 to 3 along — which is its own Jakarta migration.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Migrate to a Camel 4 LTS | Currently 4.18 or 4.22. | Jakarta migration plus integration regression | Engineering time | The destination — and note Camel LTS lines last about a year, so it is a recurring commitment. |
| OSSeva extended support | Patched Camel 3.x builds. | BOM swap | Per application estate | No Jakarta rewrite forced by a security deadline. |
What OSSeva does for Apache Camel 3
OSSeva patches this line
OSSeva ships patched Camel 2.x and 3.x builds, covering the components you actually use and the third-party libraries they bundle.
Apache Camel extended support
Apache Camel extended support What your auditor will say
Requires that system components are protected from known vulnerabilities by installing applicable security patches. A release line with no upstream patch stream cannot meet this by itself, whatever the scanner reports.
Vulnerability identification and remediation. Scanning satisfies identification. Remediation is what fails when the fix does not exist for the line you run.
Is Apache Camel 3 still supported?
No. The last 3.x release was 3.22.4 on 9 March 2025, and Camel's download page lists only 4.x LTS releases as supported.
Is Apache Camel outdated?
Camel itself is actively developed, with releases almost monthly. What goes out of date quickly is any given version: only the two most recent LTS lines are supported, for about a year each. An estate that stopped upgrading will be on an unsupported version within twelve months.
Get a quote
Still running Apache Camel 3?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.
Prefer to talk or read more first?