CVE-2026-85248: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in Apache Camel PQC component
CVE-2026-85248 key facts
- CISA KEV
- Not listed (catalogue checked )
- Highest advisory rating
- Medium
- CVSS base score
- 5.9 (Apache), 5.9 (Red Hat)
- Weakness
- CWE-347
- Fixed releases
- Apache: 4.18.5, 4.22.1
- Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
- Listed by VulniPulse
- Record changed
Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-85248; each belongs to its advisory, not to every product listed. How records are collected and checked.
How do I fix CVE-2026-85248?
Upgrade to a fixed release named by the vendor:
- Apache: 4.18.5, 4.22.1
- Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
- Signature is stateful and is not thread safe: update() accumulates the data to be signed or verified, and verify() consumes that accumulated state. (Apache)
- 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. (Apache)
Vendor advisories for CVE-2026-85248
Apache
1 advisory- Advisory severityMedium5.9
Medium [CVE-2026-85248] Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in Apache Camel PQC component
CVE-2026-85248Source published Source updated
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…
- Affected products in this advisory
- Apache Camel PQC
- Source-reported affected versions
- 4.12.0 before 4.18.5
- 4.19.0 before 4.22.1
- Source-reported fixed versions
- 4.18.5
- 4.22.1
- Mitigation guidance
- 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.
- 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.
1 more entries in the full advisory.
- Workarounds
- 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.
Red Hat
1 advisory- Advisory severityMedium5.9
Medium [CVE-2026-85248] Signature verification bypass via unsynchronized signature instance
CVE-2026-85248Source published Source updated
Signature verification bypass via unsynchronized signature instance. Red Hat rates this moderate (CVSS 5.9). Weakness: CWE-347.
- Related products — impact not confirmed
- No product details extracted. Check the source bulletin.
- Source-reported affected versions
- < 4.12.0
- < 4.18.5
- < 4.19.0
- < 4.22.1
- Source-reported fixed versions
- 4.23.0
- 4.18
- 4.18.5
- 4.22
1 more entries in the full advisory.
- Mitigation guidance
- No mitigation guidance extracted; consult the source.
References
More Apache advisories
CVE-2026-85300Oct 19, 2026Incorrect Default Permissions vulnerability in Apache Camel PQC componentCVE-2026-46590Jul 6, 2026Deserialization of Untrusted Data vulnerability in Apache Camel PQC componentCVE-2026-43867Jul 6, 2026Deserialization of Untrusted Data vulnerability in Apache Camel PQC ComponentCVE-2026-86336Nov 10, 2026Apache TomEE running on JDK 21 or later skips EJB method authorization checksCVE-2026-86531Nov 10, 2026The embedded OpenEJB HTTP server does not limit the size of incoming request bodiesCVE-2026-87758Nov 10, 2026The remote EJB client does not verify
Get an email when Apache publishes the next one.
See Apache's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
iPhone and Android apps · New on the App Store
Get alerts for new CVEs on your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
