CVE-2026-40860

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

Published Apr 27, 2026 CVSS 3.1 · 9.8 Critical EPSS 1.7% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

JmsBinding.extractBodyFromJms() in camel-jms and equivalent classes in camel-sjms, camel-sjms2, and camel-amqp deserialized incoming JMS ObjectMessage payloads without any filtering or allowlist. Because this code path is taken whenever the mapJmsMessage option is enabled, an attacker who can publish a crafted ObjectMessage to a queue or topic that a Camel application consumes can trigger arbitrary code execution via a deserialization gadget chain present on the classpath. The vulnerability is a classic unsafe deserialization flaw (CWE‑502) that allows remote attackers to execute code with the privileges of the Camel process.

Affected Systems

Apache Software Foundation’s Apache Camel is affected. The flaw exists in camel‑jms, camel‑sjms, camel‑sjms2, camel‑amqp, as well as JMS‑family components such as camel‑activemq and camel‑activemq6. The vulnerable versions are 3.0.0 through 4.14.6, 4.15.0 through 4.18.1, and 4.19.0 through 4.19.9. 4.14.x LTS users should upgrade to 4.14.7, 4.18.x users to 4.18.2, and all other users to 4.20.0 to fix the issue.

Risk and Exploitability

The CVSS score of 9.8 marks this as critical. Current EPSS indicates a very low probability of exploitation (<1%), and the vulnerability is not listed in the CISA KEV catalog. The attack requires the ability to publish a crafted ObjectMessage to a Camel-consumed JMS destination; no authentication constraints are described, so the threat exists wherever the application exposes a JMS broker entry point. Presence of a gadget chain on the classpath is also required for RCE to occur.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Camel to version 4.20.0 (or 4.14.7 if on the 4.14.x LTS stream, or 4.18.2 if on the 4.18.x stream) to obtain the deserialization safeguard.
  • Upgrade all affected Camel components (camel‑sjms, camel‑sjms2, camel‑amqp, camel‑activemq, camel‑activemq6) to the same patched Camel release to ensure consistency across the stack.
  • If an upgrade cannot be performed immediately, review the Camel configuration and either disable the mapJmsMessage option or ensure that incoming JMS messages are explicitly validated and not deserialized, and avoid consuming ObjectMessage payloads where possible.

Generated by OpenCVE AI on April 28, 2026 at 04:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-m5vh-3fw5-5wgh Apache camel-jms, camel-sjms, camel-sjms2 and camel-amqp: Unsafe Deserialization of JMS ObjectMessage
History
Type Values Removed Values Added
CPEs cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*
cpe:2.3:a:apache:camel:4.19.0:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Apache
Apache camel
Vendors & Products Apache
Apache camel
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Apache Camel: Unsafe Deserialization of JMS ObjectMessage in camel-jms, camel-sjms, camel-sjms2 and camel-amqp
Weaknesses CWE-502
References
Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Sep 10, 2026, 12:04 PM
Reserved
Apr 15, 2026, 12:44 PM
Status
Modified
Published
Apr 27, 2026, 9:16 AM
Modified
Oct 26, 2026, 10:10 PM
Severity
Important
Public date
Apr 27, 2026, 8:03 AM