-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

- ---
title: "Apache Camel Security Advisory - CVE-2026-85248"
date: 2026-10-15T10:00:00+02:00
url: /security/CVE-2026-85248.html
draft: false
type: security-advisory
cve: CVE-2026-85248
severity: MEDIUM
summary: "Camel-PQC: signature verification bypass - one java.security.Signature instance was shared across concurrent exchanges without synchronization, so interleaved use could make a verification succeed for data it never covered"
description: "The producer held a single java.security.Signature instance and used it for every exchange without synchronizing access. Signature is stateful and is not thread safe: update() accumulates the data to be signed or verified, and verify() consumes that accumulated state. With concurrent exchanges sharing one instance the update and verify calls of different messages interleave, so a verification can complete against data that belongs to another exchange, or against a partially accumulated buffer. The outcome is non-deterministic and includes a verification reporting success for a message whose signature was never actually checked, which defeats the guarantee the component exists to provide. Reaching it requires concurrent traffic through the same endpoint, which is the ordinary condition for a Camel route under load."
mitigation: "Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The Signature instance is no longer shared across concurrent exchanges. For deployments that cannot upgrade immediately, restrict the affected route to a single concurrent consumer so that no two exchanges use the instance at once."
credit: "This issue was discovered by Claude Security Scan Tool"
affected: "From 4.12.0 before 4.18.5, from 4.19.0 before 4.22.1."
fixed: 4.18.5, 4.22.1 and 4.23.0
- ---

The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24445 refers to the various commits that resolved the issue, and has more details.

The fix was merged on main in https://github.com/apache/camel/pull/25825 (commit 91d5bdac51182fda8515e5b200e8aa842ccd1bc6), backported to camel-4.22.x in https://github.com/apache/camel/pull/25850 (commit 936a851a2b92c29712a77080fa0935b361179f83) and to camel-4.18.x in https://github.com/apache/camel/pull/25851 (commit 1466b0fdf5a6e9a8fd859893f9b245218f30ea17).

The issue is classified as CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later.
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmrQ8yYACgkQ406fOAL/
QQANJwgAiVcmLp8hvtBrCFomBefoQSoBPkF32pIk/jy+6BJs/9f9dPkMExenEUgq
VrscNt1OSaYbyKvkWRBATvJn9SJ7aSRot6z9jafl1ATua3B9hPjKLksxQ24LxfqJ
fVCiLsC+eq6gV0M3tSpvdUwcqhs6TdSHMo6fcHQx+lxqAKQKI3AJiacED3S9jdH8
o16LQbV59CLo9/NmvoltQ2JQJL9rHuT8eGK7HdKwEJIURg31n5gj1BXw01mpsQev
dD5JYacfqWGEHpH/0MhFKrx7WmlBeQyFRMY3MZ3eJdAFpWdEP1cJu2p53kz6GuP+
Ijen2tSHiMwMxcaaiiST+PjvGAJzRA==
=1fT9
-----END PGP SIGNATURE-----