Apache camel-jms, camel-sjms, camel-sjms2 and camel-amqp: Unsafe Deserialization of JMS ObjectMessage
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.
Czego dotyczy
Kliknij technologię, aby zobaczyć wszystkie dotyczące jej podatności.
| Platforma | Paczka | Podatne wersje | Poprawka w wersji |
|---|---|---|---|
| Java / Kotlin (Maven) | org.apache.camel:camel-activemq | >= 3.0.0, < 4.14.7, >= 4.15.0, < 4.18.2, >= 4.19.0, < 4.20.0 | 4.14.7, 4.18.2, 4.20.0 |
| Java / Kotlin (Maven) | org.apache.camel:camel-activemq6 | >= 3.0.0, < 4.14.7, >= 4.15.0, < 4.18.2, >= 4.19.0, < 4.20.0 | 4.14.7, 4.18.2, 4.20.0 |
| Java / Kotlin (Maven) | org.apache.camel:camel-amqp | >= 3.0.0, < 4.14.7, >= 4.15.0, < 4.18.2, >= 4.19.0, < 4.20.0 | 4.14.7, 4.18.2, 4.20.0 |
| Java / Kotlin (Maven) | org.apache.camel:camel-jms | >= 3.0.0, < 4.14.7, >= 4.15.0, < 4.18.2, >= 4.19.0, < 4.20.0 | 4.14.7, 4.18.2, 4.20.0 |
| Java / Kotlin (Maven) | org.apache.camel:camel-sjms | >= 3.0.0, < 4.14.7, >= 4.15.0, < 4.18.2, >= 4.19.0, < 4.20.0 | 4.14.7, 4.18.2, 4.20.0 |
| Java / Kotlin (Maven) | org.apache.camel:camel-sjms2 | >= 3.0.0, < 4.14.7, >= 4.15.0, < 4.18.2, >= 4.19.0, < 4.20.0 | 4.14.7, 4.18.2, 4.20.0 |
Odnośniki
- https://nvd.nist.gov/vuln/detail/CVE-2026-40860
- https://github.com/apache/camel/pull/22598
- https://github.com/apache/camel/pull/22603
- https://github.com/apache/camel/pull/22604
- https://github.com/apache/camel/pull/22639
- https://github.com/apache/camel/commit/0c06142c46a1422b6b49fab784a1087c50e48ee8
- https://github.com/apache/camel/commit/107e8c279cf9bf488843e33fb6333cc2d7f37c67
- https://github.com/apache/camel/commit/6a82709f0fc5431f46d2939547aacd2c7395c97a
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-40860.json
- https://issues.apache.org/jira/browse/CAMEL-23321
- https://github.com/apache/camel/releases/tag/camel-4.20.0
- https://github.com/apache/camel/releases/tag/camel-4.18.2
- https://github.com/apache/camel/releases/tag/camel-4.14.7
- https://github.com/apache/camel
- https://camel.apache.org/security/CVE-2026-40860.html
- https://bugzilla.redhat.com/show_bug.cgi?id=2463172
- https://access.redhat.com/security/cve/CVE-2026-40860
- https://access.redhat.com/errata/RHSA-2026:22453
- https://access.redhat.com/errata/RHSA-2026:17668
- http://www.openwall.com/lists/oss-security/2026/04/26/10
- Wektor CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H- Słabość (CWE)
CWE-502- Platforma
- Java / Kotlin (Maven)
- Paczka
org.apache.camel:camel-activemq, org.apache.camel:camel-activemq6, org.apache.camel:camel-amqp- Ujawniono
- 27.04.2026
- Aktualizacja
- 11.10.2026 12:22
Źródła i licencje
OSV / GitHub Advisory Database - GHSA-m5vh-3fw5-5wgh - CC BY 4.0
Historia podatności: org.apache.camel:camel-jms
Wszystkie opisane podatności tej paczki (Java / Kotlin (Maven)), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.
- Wszystkich wpisów
- 4
- Pierwsza → ostatnia
- 04.2026 07.2026
- Bez poprawki
- 0
- Wykorzystywana w atakach
- 0
Rozkład istotności
- Krytyczna 2
- Wysoka 2
Ujawnienia w latach
- 2026: 4
-
Apache camel-jms, camel-sjms, camel-sjms2 and camel-amqp: Unsafe Deserialization of JMS ObjectMessage ten wpis
Dowiedz się, które podatności dotyczą Twojej aplikacji
Po podłączeniu integracji DockRay i włączeniu raportowania oprogramowania DockRay porównuje zgłoszone wersje komponentów ze znanymi podatnościami i powiadamia o potwierdzonych dopasowaniach. Zakres zależy od obsługiwanej technologii i dostępnych biuletynów.