Skip to content

CVE-2026-43866: bump Apache Camel to 2.25.5-TT.2 (activemq-5.15)#252

Open
jgallimore wants to merge 1 commit into
activemq-5.15.x-TT.xfrom
cve/activemq-5.15/335_CVE-2026-43866
Open

CVE-2026-43866: bump Apache Camel to 2.25.5-TT.2 (activemq-5.15)#252
jgallimore wants to merge 1 commit into
activemq-5.15.x-TT.xfrom
cve/activemq-5.15/335_CVE-2026-43866

Conversation

@jgallimore

Copy link
Copy Markdown
Member

Fix for CVE-2026-43866 — Apache Camel camel-jms ObjectMessage/DefaultExchangeHolder deserialization (CAMEL-23373).

Tracking issue: https://github.com/tomitribe/cve/issues/335
Reachability audit: https://github.com/tomitribe/cve/blob/main/docs/security-audits/2026/CVE-2026-43866.md

Changes

  • Bumped <camel-version> 2.25.22.25.5-TT.2 (Tomitribe-forked Camel). Moves the whole camel family (core/jms/spring/blueprint/jdbc/test/test-spring) to the TT build.

Rationale

camel-jms 2.25.x ships the un-gated ObjectMessage deserialization sink and there is NO fixed upstream 2.25.x release. Tomitribe forked Camel 2.25.x and backported CAMEL-23373 (new objectMessageEnabled option defaulting to false) as 2.25.5-TT.2. Resolves from repository.tomitribe.com (already declared in this branch's <repositories>).

Verification

  • Jenkins build — NOT triggered in this run (VPN/Jenkins unavailable); trigger manually. Confirms TT camel resolves.
  • Smoke test (post-merge)

Points camel-version at the Tomitribe-forked Camel 2.25.5-TT.2, which
backports CAMEL-23373 (objectMessageEnabled=false) to camel-jms 2.25.x to
fix the ObjectMessage/DefaultExchangeHolder deserialization sink. No upstream
2.25.x fix exists. Resolves from repository.tomitribe.com (already declared).

See tomitribe/cve#335

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant