fix(#712): upgrade Apache CXF to 4.1.7 (CVE-2026-44417) - #717
Open
jbonofre wants to merge 1 commit into
Open
Conversation
Bump the bundled Apache CXF from 4.1.5 to 4.1.7 to remediate CVE-2026-44417 (incomplete fix of CVE-2025-48913, remote code execution via JMS configuration), which is fixed upstream in CXF 4.1.6 / 4.2.1 / 3.6.11. 4.1.7 is the latest 4.1.x patch and stays within the existing OSGi import range [4.1,4.2). The cxf-codegen-plugin version is moved in lockstep. The camel-cxf-all bundle shades all org.apache.cxf:* artifacts via ${cxf-version}, so the rebuilt bundle embeds and re-exports CXF 4.1.7.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Upgrades the bundled Apache CXF from
4.1.5to4.1.7.Closes #712.
Why
CXF
< 4.1.6is affected by CVE-2026-44417 — an incomplete fix of CVE-2025-48913, allowing remote code execution when an untrusted party can influence the JMS configuration (CWE-20). It is fixed upstream in CXF 4.1.6 / 4.2.1 / 3.6.11.4.1.7is the latest4.1.xpatch: it carries the CVE fix plus subsequent4.1.xfixes and stays within the existing OSGi import range[4.1,4.2), so no other feature/import changes are required.Per the camel-karaf security model, the vulnerability lives in Apache CXF (a packaged component); camel-karaf's role here is solely the bundled-version upgrade.
Changes
pom.xml:cxf-version4.1.5→4.1.7, andcxf-codegen-plugin-versionmoved in lockstep. Thecxf-xjc-*plugins are a separately versioned artifact family and are left unchanged.The
camel-cxf-allbundle shades everyorg.apache.cxf:*artifact via${cxf-version}, so the rebuilt bundle embeds and re-exports CXF4.1.7.Verification
mvn clean installof allcamel-cxfmodules (camel-cxf,camel-cxf-all,camel-cxf-blueprint,camel-cxf-spring-all,camel-cxf-transport-blueprint,camel-cxf-transport-jetty) — passes.camel-cxf-allbundle:Export-Packageadvertisesorg.apache.cxf*;version="4.1.7"and the embeddedcxf-core/pom.propertiesreportsversion=4.1.7.camel-cxf,camel-cxf-jetty, andcamel-cxf-springfeatures resolve cleanly.Notes for reviewers
CVE-2026-44417 is already public and fixed upstream, and issue #712 is public and assigned — so this is a normal public dependency-bump PR (no embargo).