Skip to content
Fencer Vulns
critical 9.8

CVE-2026-40860 in the critical feed json

Apache Camel: Unsafe Deserialization of JMS ObjectMessage in camel-jms, camel-sjms, camel-sjms2 and camel-amqp

published 2026-04-27 6 mo ago modified 2026-10-26 13 d ago also EUVD-2026-25794 , GHSA-m5vh-3fw5-5wgh

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.camel:camel-jms 4.14.7, 4.18.2, 4.20.0
  • maven org.apache.camel:camel-sjms 4.14.7, 4.18.2, 4.20.0
  • maven org.apache.camel:camel-sjms2 4.14.7, 4.18.2, 4.20.0
  • maven org.apache.camel:camel-amqp 4.14.7, 4.18.2, 4.20.0
  • maven org.apache.camel:camel-activemq 4.14.7, 4.18.2, 4.20.0
  • maven org.apache.camel:camel-activemq6 4.14.7, 4.18.2, 4.20.0
  • Apache Software Foundation Apache Camel 4.14.7, 4.18.2, 4.20.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-40860 updated cvss 7.5

Apache Camel: camel-jms: camel-sjms: camel-sjms2: camel-amqp: camel-activemq: camel-activemq6: Apache Camel: Remote Code Execution via deserialization of JMS ObjectMessage

  • Red Hat build of Apache Camel 4 for Quarkus 3 camel-jms, camel-amqp
    affected: no fix available
  • Red Hat Build of Apache Camel 4.18 for Quarkus 3.33
    fixed: vendor fix RHSA-2026:22453
  • Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14
    fixed: vendor fix RHSA-2026:17668
  • Red Hat Fuse 7 camel-jms, camel-amqp, camel-jms-starter Red Hat JBoss Enterprise Application Platform 8 camel-jms, camel-amqp Red Hat JBoss Enterprise Application Platform Expansion Pack camel-jms, camel-amqp
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
6 mo ago

Exploit prediction

1.74% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
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
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
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
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
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
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

Affected products

  • Apache Software Foundation Apache Camel
  • Red Hat Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14
  • Red Hat Red Hat Build of Apache Camel 4.18 for Quarkus 3.33
  • Red Hat Red Hat build of Apache Camel 4 for Quarkus 3
  • Red Hat Red Hat Fuse 7
  • Red Hat Red Hat JBoss Enterprise Application Platform 8
  • Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.