How to Fix CVE-2026-40860: Apache Camel (Bundle Sibling)
By Sai Kiran Pandrala
Last verified: 2026-05-25
CVE-2026-40860 is a sibling vulnerability in the same vendor advisory as CVE-2026-27172. Applying the patched build named in the primary write-up closes this CVE as well.
| Severity | CVSS 9.8 - Critical |
|---|---|
| Actively exploited? | Not currently in CISA KEV |
| Affected | Same as the bundle - see CVE-2026-27172 |
| Fixed in | Same patched build as CVE-2026-27172 (See vendor advisory) |
| Type (CWE) | CWE-502: CWE-502 Deserialization of Untrusted Data |
What's different about CVE-2026-40860?
JmsBinding.extractBodyFromJms() in camel-jms, and the equivalent JmsBinding class in camel-sjms, deserialized the payload of incoming JMS ObjectMessage values via javax.jms.ObjectMessage.getObject() without applying any ObjectInputFilter, class allowlist or class denylist.
The technical impact and remediation are identical to the primary CVE in the bundle. The same vendor patch closes both.
How to fix CVE-2026-40860
Apply the patched build per the primary write-up: How to Fix CVE-2026-27172.
The patch installation procedure, verification commands, and interim mitigations are documented there. Reusing one runbook keeps the rollout consistent across the bundle.
Frequently asked questions
Is CVE-2026-40860 fixed by the same patch as CVE-2026-27172?
Yes. CVE-2026-40860 ships in the same vendor advisory as CVE-2026-27172. Applying the patched build named in the primary write-up closes both.
What is the CVSS score for CVE-2026-40860?
The CVSS base score is 9.8 (Critical).
Is it being exploited?
It is not currently listed in CISA KEV.
References
- Official vendor advisory: https://camel.apache.org/security/CVE-2026-40860.html
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-40860
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary write-up: How to Fix CVE-2026-27172
*Part of the Apache Camel bundle. Full procedure at CVE-2026-27172.*