Description
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.
Published: 2026-10-19
Score: 5.9 Medium
EPSS: n/a
KEV: No
Impact: Signature Verification Bypass
Action: Immediate Patch
AI Analysis

Impact

The vulnerability arises because the PQC component of Apache Camel uses a single stateful java.security.Signature instance for all exchanges without synchronizing access. Since the Signature class accumulates data for signing or verification and is not thread‑safe, concurrent exchanges interleave update() and verify() calls. This race condition can allow a verification to succeed against data that does not belong to the message being processed or against partially accumulated data, effectively bypassing the intended cryptographic check and deceiving the caller into trusting an unverified payload.

Affected Systems

Apache Software Foundation’s Apache Camel, from version 4.12.0 up to, but not including, 4.18.5, and from 4.19.0 up to, but not including, 4.22.1 are affected. Users on the 4.18.x LTS stream should upgrade to 4.18.5; users on the 4.22.x LTS stream should upgrade to 4.22.1; the latest fix is available in version 4.23.0.

Risk and Exploitability

The CVSS score of 5.9 indicates moderate severity. EPSS data is unavailable, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires concurrent traffic through the same Camel endpoint, a condition that is common under normal load. While there are no public reports of exploitation, the race condition can be engineered to force false signature verification, which undermines authentication and data integrity.

Generated by OpenCVE AI on October 19, 2026 at 13:25 UTC.

Remediation

Vendor Solution

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.

Vendor Workaround

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.

OpenCVE Recommended Actions

  • Upgrade Apache Camel to the latest patched version (4.23.0, or 4.18.5/4.22.1 depending on your LTS stream).
  • If an upgrade cannot be performed immediately, restrict the affected Camel route to a single concurrent consumer so that no two exchanges share the same Signature instance.
  • Ensure that any custom code accesses the Signature instance with proper synchronization to prevent race conditions (CWE‑362).

Generated by OpenCVE AI on October 19, 2026 at 13:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 19 Oct 2026 11:00:00 +0000

Type Values Removed Values Added
Description 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.
Title Apache Camel: Camel-PQC Signature Verification Bypass via a Shared Unsynchronized Signature Instance
Weaknesses CWE-362
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N'}

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-10-19T10:34:16.177Z

Reserved: 2026-09-03T16:26:19.164Z

Link: CVE-2026-85248

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-19T11:17:22.970

Modified: 2026-10-19T11:17:22.970

Link: CVE-2026-85248

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-19T13:30:14Z

Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')