# CVE-2026-40860: Apache Camel: Unsafe Deserialization of JMS ObjectMessage in camel-jms, camel-sjms, camel-sjms2 and camel-amqp > An attacker can achieve remote code execution by publishing a crafted JMS ObjectMessage to a queue consumed by an Apache Camel application. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 27 Apr 2026 - **Updated:** 10 Sep 2026 - **Also known as:** GHSA-m5vh-3fw5-5wgh, MINI-c4j9-24m4-gpj3, MINI-pgqq-rfwm-3855, MINI-vh7x-fxmv-8w4x, MINI-xvq4-w8cq-7gc7 ## What is CVE-2026-40860? CVE-2026-40860 is a critical unsafe deserialization vulnerability in Apache Camel, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Because this code path is reached whenever the mapJmsMessage option is enabled (the default) and Camel acts as a JMS consumer, an attacker able to publish a crafted ObjectMessage to a queue or topic consumed by a Camel application could achieve remote code execution when a deserialization gadget chain was present on the classpath. The same handling was reached transitively through camel-sjms2 (whose Sjms2Endpoint extends SjmsEndpoint) and through camel-amqp (whose AMQPJmsBinding extends JmsBinding), and by other JMS-family components built on JmsComponent such as camel-activemq and camel-activemq6. This issue affects Apache Camel: from 3.0.0 before 4.14.7, from 4.15.0 before 4.18.2, from 4.19.0 before 4.20.0. Users are recommended to upgrade to version 4.20.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.7. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.2. Weakness: CWE-502 (Deserialization of Untrusted Data) ## Which versions are affected by CVE-2026-40860? 36 open source packages ship an affected version, including org.apache.camel:camel-activemq, org.apache.camel:camel-activemq6 and org.apache.camel:camel-amqp. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.camel:camel-activemq` | Maven | From 3.0.0 | 4.14.7 | | `org.apache.camel:camel-activemq` | Maven | From 3.0.0 | 4.14.7 | | `org.apache.camel:camel-activemq` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-activemq` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-activemq` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-activemq` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-activemq6` | Maven | From 3.0.0 | 4.14.7 | | `org.apache.camel:camel-activemq6` | Maven | From 3.0.0 | 4.14.7 | | `org.apache.camel:camel-activemq6` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-activemq6` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-activemq6` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-activemq6` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-amqp` | Maven | From 3.0.0 | 4.14.7 | | `org.apache.camel:camel-amqp` | Maven | From 3.0.0 | 4.14.7 | | `org.apache.camel:camel-amqp` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-amqp` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-amqp` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-amqp` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-jms` | Maven | From 3.0.0 | 4.14.7 | | `org.apache.camel:camel-jms` | Maven | From 3.0.0 | 4.14.7 | | `org.apache.camel:camel-jms` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-jms` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-jms` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-jms` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-sjms` | Maven | From 3.0.0 | 4.14.7 | | `org.apache.camel:camel-sjms` | Maven | From 3.0.0 | 4.14.7 | | `org.apache.camel:camel-sjms` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-sjms` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-sjms` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-sjms` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-sjms2` | Maven | From 3.0.0 | 4.14.7 | | `org.apache.camel:camel-sjms2` | Maven | From 3.0.0 | 4.14.7 | | `org.apache.camel:camel-sjms2` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-sjms2` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-sjms2` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-sjms2` | Maven | From 4.19.0 | 4.20.0 | Products: Apache Camel. ## How do I fix CVE-2026-40860? Upgrade org.apache.camel:camel-activemq to a fixed version for your release line: 4.14.7, 4.18.2 or 4.20.0. ## Is CVE-2026-40860 being exploited? There is no known exploitation of CVE-2026-40860 in the wild and no public exploit code. Public exploit code: - Reproducer for CVE-2026-40860 — Apache Camel camel-jms/sjms/amqp JMS ObjectMessage unsafe deserialization (RCE) (github_poc): https://github.com/oscerd/CVE-2026-40860 ## Other vulnerabilities in Apache Camel - [CVE-2026-33453](https://insights.sbomify.com/CVE-2026-33453/): Apache camel-coap allows header injection that can lead to remote code execution (critical 10.0) - [CVE-2026-40453](https://insights.sbomify.com/CVE-2026-40453/): Apache Camel has an incomplete fix for CVE-2025-27636 (critical 9.9) - [CVE-2026-80351](https://insights.sbomify.com/CVE-2026-80351/): Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod (critical 9.8) - [CVE-2026-80352](https://insights.sbomify.com/CVE-2026-80352/): Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects (critical 9.8) - [CVE-2026-71300](https://insights.sbomify.com/CVE-2026-71300/): Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-40860 and fix it if it is affected. What it is: CVE-2026-40860 is a critical unsafe deserialization vulnerability in Apache Camel, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-40860 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.camel:camel-activemq (Maven): affected from 3.0.0; fixed in 4.14.7 - org.apache.camel:camel-activemq (Maven): affected from 3.0.0; fixed in 4.14.7 - org.apache.camel:camel-activemq (Maven): affected from 4.15.0; fixed in 4.18.2 - org.apache.camel:camel-activemq (Maven): affected from 4.15.0; fixed in 4.18.2 - org.apache.camel:camel-activemq (Maven): affected from 4.19.0; fixed in 4.20.0 - org.apache.camel:camel-activemq (Maven): affected from 4.19.0; fixed in 4.20.0 - org.apache.camel:camel-activemq6 (Maven): affected from 3.0.0; fixed in 4.14.7 - org.apache.camel:camel-activemq6 (Maven): affected from 3.0.0; fixed in 4.14.7 - org.apache.camel:camel-activemq6 (Maven): affected from 4.15.0; fixed in 4.18.2 - org.apache.camel:camel-activemq6 (Maven): affected from 4.15.0; fixed in 4.18.2 - org.apache.camel:camel-activemq6 (Maven): affected from 4.19.0; fixed in 4.20.0 - org.apache.camel:camel-activemq6 (Maven): affected from 4.19.0; fixed in 4.20.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-40860/ (Markdown: https://insights.sbomify.com/CVE-2026-40860/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40860 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40860 - OSV: https://osv.dev/vulnerability/CVE-2026-40860 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-40860/ Summaries are generated and may contain mistakes; the official description above is the record.