Back to CVE records
Medium 5.9Published Oct 19, 2026

CVE-2026-85248Apache Camel: Camel-PQC Signature Verification Bypass via a Shared Unsynchronized Signature Instance

Updated under an hour ago ()

Does this affect you?

It affects Apache Software Foundation Apache Camel. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in Apache Camel PQC component. This issue affects Apache Camel: from 4.12.0 before 4.18.5, from 4.19.0 before 4.22.1. 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. 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.

CVSS
5.9 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Weakness (CWE)
CWE-362
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
apache
NVD analysis
Received
Record last updated
Oct 19, 2026
First seen by InfoSec Signals
Oct 19, 2026

Affected products

Affected products
Apache Software Foundation Apache Camel
apache_software_foundation:apache_camel (from the name)
from 4.12.0 before 4.18.5; from 4.19.0 before 4.22.1; 4.18.5 not affected; 4.22.1 not affected; 4.23.0 not affected
CNA record

References

  • vendor-advisory
  • issue-tracking
  • patch
  • patch
  • patch

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.