Skip to content
VulniPulse
Critical9.8Apache Software Foundation

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

This Apache advisory covers CVE-2026-40860 in Apache Camel and ActiveMQ.

Open the Apache advisory

Key facts

Vendor rating
Critical, CVSS 9.8
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H · base score 9.8, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: high. Availability impact: high.
Weakness
  • CWE-502 Deserialization of Untrusted Data
EPSS
1.74% chance of exploitation in the next 30 days (78th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: total. CISA, .
CISA KEV
Not listed (catalogue checked )
Affected
Apache Camel 3.0.0 before 4.14.7; Apache Camel 4.15.0 before 4.18.2; Apache Camel 4.19.0 before 4.20.0
Fixed in
4.14.7, 4.18.2, 4.20.0
Source published
Source revised
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

Apache Software FoundationMessagingActiveMQ

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.

Text from the source record.

Affected versions
  • Apache Camel 3.0.0 before 4.14.7
  • Apache Camel 4.15.0 before 4.18.2
  • Apache Camel 4.19.0 before 4.20.0

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-40860

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

  • Users are recommended to upgrade to version 4.20.0, which fixes the issue.

CVE-2026-40860 in other vendors' advisories

Compare every advisory for CVE-2026-40860

Apache Software Foundation advisories, April 2026All Apache Software Foundation advisories

Get an email when Apache Messaging (ActiveMQ/Kafka/Pulsar) publishes the next one.

See Apache Messaging (ActiveMQ/Kafka/Pulsar)'s last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache Messaging (ActiveMQ/Kafka/Pulsar)