← Search results
CVE-LINKED INVENTORY45 SECURITY RECORDS
Apache Software Foundation
Apache CXF
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-57818 | 6 Aug 2026 | 4.2.0 < 4.2.3; 4.0.0 < 4.1.8; < 3.6.12 | 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-61466 | 6 Aug 2026 | < 3.6.12; 4.0.0 < 4.1.8; 4.2.0 < 4.2.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-63687 | 6 Aug 2026 | 4.2.0 < 4.2.3; 4.0.0 < 4.1.8; < 3.6.12 | 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-65583 | 6 Aug 2026 | 4.2.0 < 4.2.3; 4.0.0 < 4.1.8; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-68079 | 6 Aug 2026 | 4.2.0 < 4.2.3; 4.0.0 < 4.1.8; < 3.6.12 | 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-68481 | 6 Aug 2026 | 4.2.0 < 4.2.3; 4.0.0 < 4.1.8; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-65432 | 6 Aug 2026 | 4.2.0 < 4.2.3; 4.0.0 < 4.1.8; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-57817 | 6 Aug 2026 | 4.2.0 < 4.2.3; 4.0.0 < 4.1.8; < 3.6.12 | 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-66909 | 6 Aug 2026 | 4.2.0 < 4.2.3; 4.0.0 < 4.1.8; < 3.6.12 | 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-64958 | 6 Aug 2026 | 4.2.0 < 4.2.3; 4.0.0 < 4.1.8; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-57819 | 6 Aug 2026 | 4.2.0 < 4.2.3; 4.0.0 < 4.1.8; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-54225 | 6 Aug 2026 | 4.2.0 < 4.2.3; 4.0.0 < 4.1.8; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-50645 | 12 Jun 2026 | 4.2.0 < 4.2.2; 4.0.0 < 4.1.7; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-50634 | 12 Jun 2026 | 4.2.0 < 4.2.2; 4.0.0 < 4.1.7; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-50633 | 12 Jun 2026 | 4.2.0 < 4.2.2; 4.0.0 < 4.1.7; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-50632 | 12 Jun 2026 | 4.2.0 < 4.2.2; 4.0.0 < 4.1.7; < 3.6.12 | Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-50631 | 12 Jun 2026 | 4.2.0 < 4.2.2; 4.0.0 < 4.1.7; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-50630 | 12 Jun 2026 | 4.2.0 < 4.2.2; 4.0.0 < 4.1.7; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-50629 | 12 Jun 2026 | 4.2.0 < 4.2.2; 4.0.0 < 4.1.7; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-50628 | 12 Jun 2026 | 4.2.0 < 4.2.2; 4.0.0 < 4.1.7; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-50627 | 12 Jun 2026 | 4.2.0 < 4.2.2; 4.0.0 < 4.1.7; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-49875 | 12 Jun 2026 | 4.2.0 < 4.2.2; 4.0.0 < 4.1.7; < 3.6.12 | Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-50623 | 12 Jun 2026 | 4.2.0 < 4.2.2; 4.0.0 < 4.1.7; < 3.6.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-44417 | 22 May 2026 | 4.2.0 < 4.2.1; 4.0.0 < 4.1.6; < 3.6.11 | Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-44618 | 22 May 2026 | 4.2.0 < 4.2.1; 4.0.0 < 4.1.6; < 3.6.11 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-44930 | 22 May 2026 | 4.2.0 < 4.2.1; 4.0.0 < 4.1.6; < 3.6.11 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-48913 | 8 Aug 2025 | 4.1.0 < 4.1.3; 4.0.0 < 4.0.9; < 3.6.8 | Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-48795 | 15 Jul 2025 | 3.5.10 < 3.5.11; 3.6.5 < 3.6.6; 4.0.6 < 4.0.7; 4.1.0 < 4.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-23184 | 21 Jan 2025 | < 3.5.10; 3.6.0 < 3.6.5; 4.0.0 < 4.0.6 | Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-41172 | 19 Jul 2024 | 3.6.0, 4.0.0 < 3.6.4, 4.0.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-32007 | 19 Jul 2024 | < 4.0.5, 3.6.4, 3.5.9 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29736 | 19 Jul 2024 | < 3.5.9, 3.6.4, 4.0.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-28752 | 15 Mar 2024 | < 4.0.4, 3.6.3, 3.5.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-46364 | 13 Dec 2022 | < 3.5.5; < 3.4.10 | Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2022-46363 | 13 Dec 2022 | 3.5 < 3.5.5; 3.4 < 3.4.10 | Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2021-30468 | 16 Jun 2021 | Apache CXF < 3.4.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-2021-22696 | 2 Apr 2021 | unspecified < 3.4.3; unspecified < 3.3.10 | 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-2020-13954 | 12 Nov 2020 | unspecified < 3.4.1; unspecified < 3.3.8 | 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-2018-8039 | 2 Jul 2018 | prior to 3.1.16; 3.2.x prior to 3.2.5 | 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-2017-12624 | 14 Nov 2017 | prior to 3.1.14; 3.2.x prior to 3.2.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-3156 | 10 Aug 2017 | prior to 3.0.13; 3.1.x prior to 3.1.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2016-8739 | 10 Aug 2017 | prior to 3.0.12; 3.1.x prior to 3.1.9 | 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-2016-6812 | 10 Aug 2017 | prior to 3.0.12; 3.1.x prior to 3.1.9 | 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-2017-5656 | 18 Apr 2017 | 3.1.x before 3.1.11; versions before 3.0.13 | 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-2017-5653 | 18 Apr 2017 | prior to 3.0.13; 3.1.x prior to 3.1.11 | 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 ↗ |
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.