Apache Camel: Camel-PQC Signature Verification Bypass via a Shared Unsynchronized Signature Instance
CVSS score
5.9
EPSS probability
—
Risk score
0.6
Published
19 h ago
Etkilenen ürün ve sürüm için yayımlanan güvenlik güncellemesini uygulayın.
Impact on My Inventory
Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.
Checking session…
Vulnerability description
CVE AI research
DayBreach AI Explanation
Verified against sourcesSources read
1
Source agreement
Tam uyum
Evidence confidence
%55
Short explanation
A race condition vulnerability exists in the Apache Camel PQC component due to improper synchronization using shared resources. This flaw can cause signature verification to succeed for unverified messages.
This vulnerability defeats the verification guarantee provided by the component, potentially allowing invalid or unverified data to be processed.
What should be done?
- Upgrade to Apache Camel 4.23.0 or applicable LTS releases
- Restrict the affected route to a single concurrent consumer
Chain of evidence and sources
CVE-2026-85248 zafiyeti, Apache Camel PQC bileşenindeki paylaşılan kaynak senkronizasyon sorunundan kaynaklanır.
Zafiyetin istismarı, aynı uç nokta üzerinden eşzamanlı trafik akışını gerektirir.
Show the technical text from the sources
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 vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
CWE: CWE-362
Explanation produced with the local gemini-flash-lite-latest model. Numerical metrics and the KEV, patch and exploit statuses are not determined by AI.
IMPACT: Affected Products and Software
Affected Products
The following products are affected by CVE-2026-85248 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.
| ID | VENDOR | PRODUCT | ACTION |
|---|---|---|---|
| 1 | Apache Software Foundation | Apache Camel | View |
RED HAT CSAF/VEX: Product Impact Check
SCORING: CVSS from Multiple Sources
CVSS Scores
The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.
| SCORE | VERSION | SEVERITY | VECTOR | SOURCE |
|---|---|---|---|---|
| 5.9 | CVSS V31 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N | NVD |
| 5.9 | CVSS V3_1 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N | CVE CNA |
Patch and Remediation Guide
Solution & Remediation Advisory
6 doğrulanmış yama veya düzeltilmiş sürüm kanıtı bulundu.
Backport to camel-4.22.x, released in 4.22.1 (commit 936a851a2b92c29712a77080fa0935b361179f83)
Open sourceBackport to camel-4.18.x, released in 4.18.5 (commit 1466b0fdf5a6e9a8fd859893f9b245218f30ea17)
Open sourceFix on main, released in 4.23.0 (commit 91d5bdac51182fda8515e5b200e8aa842ccd1bc6)
Open sourceBackport to camel-4.22.x, released in 4.22.1 (commit 936a851a2b92c29712a77080fa0935b361179f83)
Open sourceBackport to camel-4.18.x, released in 4.18.5 (commit 1466b0fdf5a6e9a8fd859893f9b245218f30ea17)
Open sourcePublic exploit and active exploitation status
Verified exploit intelligence
No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.
Weakness Classification and Attack Patterns (CWE & CAPEC)
CWE - Common Weakness Enumeration
While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-85248 is associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-85248 weaknesses.
Attack Vector and Accessibility
Official Sources and Advisories
CVSS Vector Radar Chart
5.9 / 10Vulnerability Scoring Details
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:NYama doğrulandı
Weakness Type (CWE & CAPEC)
Similar Vulnerabilities
Get this vulnerability through the API
Affected products, version ranges, exploitation status and patch information in a single request, with a free key.
curl -H "x-api-key: $DAYBREACH_API_KEY" \ "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-85248"