← Search results
CVE-LINKED INVENTORY50 SECURITY RECORDS
Apache Software Foundation
Apache Camel
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-78329 | 24 Aug 2026 | 4.11.0 < 4.14.9; 4.15.0 < 4.18.4; 4.19.0 < 4.22.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-71300 | 24 Aug 2026 | 4.0.0 < 4.14.9; 4.15.0 < 4.18.4; 4.19.0 < 4.22.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-63621 | 24 Aug 2026 | 3.15.0 < 4.14.9; 4.15.0 < 4.18.4; 4.19.0 < 4.21.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-66908 | 24 Aug 2026 | 4.8.0 < 4.22.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-66907 | 24 Aug 2026 | 4.0.0 < 4.14.9; 4.15.0 < 4.18.4; 4.19.0 < 4.22.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-66906 | 24 Aug 2026 | 4.0.0 < 4.14.9; 4.15.0 < 4.18.4; 4.19.0 < 4.22.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-60093 | 24 Aug 2026 | 4.0.0 < 4.14.9; 4.15.0 < 4.18.4; 4.19.0 < 4.22.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-59230 | 24 Aug 2026 | 2.17.0 < 4.14.9; 4.15.0 < 4.18.4; 4.19.0 < 4.22.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-46588 | 6 Jul 2026 | ≤ 4.14.7; 4.15.0 ≤ 4.18.2; 4.19.0 ≤ 4.20.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-46587 | 6 Jul 2026 | ≤ 4.14.7; 4.15.0 ≤ 4.18.2; 4.19.0 ≤ 4.20.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-49042 | 6 Jul 2026 | 4.8.0 ≤ 4.18.2; 4.19.0 ≤ 4.20.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-43866 | 6 Jul 2026 | 3.0.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.21.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-43867 | 6 Jul 2026 | 4.18.0 < 4.18.3; 4.19.0 < 4.21.0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-49365 | 6 Jul 2026 | 4.0.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.21.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-49098 | 6 Jul 2026 | 4.0.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.21.0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-49097 | 6 Jul 2026 | 4.0.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.21.0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-48204 | 6 Jul 2026 | 4.0.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.21.0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-48203 | 6 Jul 2026 | 4.0.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.21.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-46592 | 6 Jul 2026 | 4.0.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.21.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-46591 | 6 Jul 2026 | 4.10.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.21.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-46590 | 6 Jul 2026 | 4.18.0 < 4.18.3; 4.19.0 < 4.21.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-46457 | 6 Jul 2026 | 4.0.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.21.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-46456 | 6 Jul 2026 | 4.0.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.21.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-46455 | 6 Jul 2026 | 4.18.0 < 4.18.3; 4.19.0 < 4.21.0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-46454 | 6 Jul 2026 | 4.0.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.21.0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-46453 | 6 Jul 2026 | 4.3.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.21.0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-43865 | 6 Jul 2026 | 4.0.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.21.0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-42527 | 6 Jul 2026 | 4.14.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.21.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-40859 | 6 Jul 2026 | 4.0.0 < 4.14.8; 4.15.0 < 4.18.3; 4.19.0 < 4.20.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-40047 | 6 Jul 2026 | 4.15.0 < 4.18.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-47323 | 19 May 2026 | 3.18.0 < 4.14.6; 4.15.0 < 4.18.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-27172 | 27 Apr 2026 | 3.0.0 < 4.14.6; 4.15.0 < 4.18.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-33453 | 27 Apr 2026 | 4.14.0 ≤ 4.14.5; 4.18.0 < 4.18.1; 4.19.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-33454 | 27 Apr 2026 | 3.0.0 < 4.14.6; 4.15.0 < 4.18.1 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-40858 | 27 Apr 2026 | Apache Camel: 4.0.0 < 4.14.7, 4.15.0 < 4.18.2, 4.19.0 < 4.20.0 | RHSA-2026:22453: Red Hat Build of Apache Camel 4.18 for Quarkus 3.33 | Update reference ↗ |
| CVE-2026-40860 | 27 Apr 2026 | Apache Camel: 3.0.0 < 4.14.7, 4.15.0 < 4.18.2, 4.19.0 < 4.20.0 | RHSA-2026:22453: Red Hat Build of Apache Camel 4.18 for Quarkus 3.33 | Update reference ↗ |
| CVE-2026-23552 | 23 Feb 2026 | 4.15.0 < 4.18.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-30177 | 1 Apr 2025 | 4.10.0 < 4.10.3; 4.8.0 < 4.8.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-29891 | 12 Mar 2025 | 4.10.0 < 4.10.2; 4.8.0 < 4.8.5; 3.10.0 < 3.22.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27636 | 9 Mar 2025 | 4.10.0 < 4.10.2; 4.8.0 < 4.8.5; 3.10.0 < 3.22.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-22371 | 26 Feb 2024 | 3.21.x ≤ 3.21.3; 3.22.x ≤ 3.22.0; 4.0.x ≤ 4.0.3; 4.x ≤ 4.3.0 | 1.x ≤ 1.6.0 | Update reference ↗ |
| CVE-2024-23114 | 20 Feb 2024 | 3.0.0 < 3.21.4; 3.22.0 < 3.22.1; 4.0.0 < 4.0.4; 4.1.0 < 4.4.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-22369 | 20 Feb 2024 | 3.0.0 < 3.21.4; 3.22.0 < 3.22.1; 4.0.0 < 4.0.4; 4.1.0 < 4.4.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-8041 | 17 Sep 2018 | Camel 2.20.0 to 2.20.3, Camel 2.21.0 to 2.21.1 and Camel 2.22.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-8027 | 31 Jul 2018 | 2.20.0 to 2.20.3; 2.21.0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2017-12634 | 15 Nov 2017 | 2.19.0 to 2.19.3; 2.20.0; The unsupported Camel 2.x (2.18 and earlier) versions may be also affected. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-12633 | 15 Nov 2017 | 2.19.0 to 2.19.3; 2.20.0; The unsupported Camel 2.x (2.18 and earlier) versions may be also affected. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2016-8749 | 28 Mar 2017 | 2.16.0 to 2.16.4; 2.17.0 to 2.17.4; 2.18.0 to 2.18.1; The unsupported Camel 2.x (2.14 and earlier) versions may be also affected. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-5643 | 16 Mar 2017 | 2.17.0 to 2.17.5; 2.18.0 to 2.18.2; The unsupported Camel 2.x (2.16 and earlier) versions may be also affected. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-3159 | 7 Mar 2017 | 2.17.0 to 2.17.4; 2.18.0 to 2.18.1; The unsupported Camel 2.x (2.14 and earlier) versions may be also affected. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.