CVE-2026-42527: bump Apache Camel to 4.14.8 (activemq-6.1)#248
Open
jgallimore wants to merge 1 commit into
Open
CVE-2026-42527: bump Apache Camel to 4.14.8 (activemq-6.1)#248jgallimore wants to merge 1 commit into
jgallimore wants to merge 1 commit into
Conversation
Bumps the camel-version property (drives camel-bom) from 4.14.7 to 4.14.8, which contains the CAMEL-23372 fix for the camel-jms default ObjectInputFilter DNS side-channel. Defense-in-depth: not reachable by a default broker, but the ActiveMQ Camel integration is a shipped feature. See audit + tracking issue. See tomitribe/cve#327 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Fix for CVE-2026-42527 — Apache Camel deserialization DNS side-channel (default ObjectInputFilter, CAMEL-23372).
Tracking issue: https://github.com/tomitribe/cve/issues/327
Reachability audit: https://github.com/tomitribe/cve/blob/main/docs/security-audits/2026/CVE-2026-42527.md
Changes
<camel-version>(root pom property driving the camel-bom import)4.14.7→4.14.8. Moves the whole Camel family incl. camel-jms.Rationale
Defense-in-depth. The audit found this branch is NOT reachable by a default ActiveMQ broker (stock activemq.xml runs no Camel route), but camel-jms 4.14.7 is shipped and the ActiveMQ↔Camel integration is a supported feature — a customer who enables a Camel JMS route consuming ObjectMessages IS exposed. 4.14.8 is the fix release for the 4.14 line (patch bump, no API change).
How the dep was found
camel-jms is pulled via the
camel-bomimport in the root pom, version-governed by the<camel-version>property. Single-line property bump moves it.Verification