Apache Camel 4.22 · Version Status
Apache Camel 4.22 End of Life Date
Apache Camel 4.22 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Apache Camel 4.22 is actively supported. EOL date: August 11, 2027.
📅 Get reminded before Apache Camel 4.22 reaches EOL on August 11, 2027 — alerts 90, 30 & 7 days out.
EOL Date
Aug 11, 2027
364 days remaining
Latest Release
4.22.0
LTS release
Release Date
Aug 11, 2026
Apache Camel 4.22 series
Lifecycle detail
Apache Camel 4.22 was released on August 11, 2026 and support is scheduled to end on August 11, 2027 — a planned supported lifespan of 1 year, in line with the 1 year median for Apache Camel LTS releases. It is a long-term support (LTS) release, so it carries a longer patch window than the interim releases around it. Its most recent patch is 4.22.0, published August 7, 2026.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
All Apache Camel Versions
| Version | Latest | EOL Date | Status |
|---|
| 3.0 |
3.0.1 |
Feb 20, 2020 |
EOL |
| 2.25 LTS |
2.25.4 |
Jan 31, 2022 |
EOL |
| 3.1 |
3.1.0 |
Apr 1, 2020 |
EOL |
| 3.2 |
3.2.0 |
May 10, 2020 |
EOL |
| 3.3 |
3.3.0 |
Jun 14, 2020 |
EOL |
| 3.4 LTS |
3.4.6 |
Jun 30, 2021 |
EOL |
| 3.5 |
3.5.0 |
Oct 16, 2020 |
EOL |
| 3.6 |
3.6.0 |
Dec 11, 2020 |
EOL |
What does Apache Camel 4.22 end of life mean?
When Apache Camel 4.22 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Apache Camel 4.22 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Apache Camel 4.22 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Apache Camel 4.22 reach end of life?
Apache Camel 4.22 reached end of life on August 11, 2027. That is 364 days remaining.
Is Apache Camel 4.22 still supported?
Yes, Apache Camel 4.22 is currently supported. The EOL date is August 11, 2027.
What should I upgrade to from Apache Camel 4.22?
The recommended upgrade from Apache Camel 4.22 is
Apache Camel 4.22 — the latest actively supported version. Check the
Apache Camel full timeline for all supported versions.
What are the security risks of running Apache Camel 4.22 past EOL?
When Apache Camel 4.22 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Apache Camel should migrate immediately or implement compensating controls.