Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Back to vulnerabilities
Critical

Unsafe Deserialization of JMS ObjectMessage in Apache Camel

IdentifiersCVE-2026-40860CWE-502· Deserialization of Untrusted Data

CVE-2026-40860 is an unsafe deserialization vulnerability in Apache Camel JMS-related components, including camel-jms and the equivalent JmsBinding implementation in camel-sjms, with the same vulnerable handling reached transitively through camel-sjms2 and camel-amqp, and affecting other JMS-family components built on JmsComponent such as camel-activemq and camel-activemq6. The flaw is in JMS consumer-side handling of incoming javax.jms.ObjectMessage instances: JmsBinding.extractBodyFromJms() in camel-jms, and the corresponding JmsBinding logic in camel-sjms, call ObjectMessage.getObject() and deserialize attacker-controlled message content without applying an ObjectInputFilter, class allowlist, or class denylist. The vulnerable path is reached when Camel acts as a JMS consumer and the mapJmsMessage option is enabled, which is the default. As a result, a crafted ObjectMessage published to a queue or topic consumed by a vulnerable Camel application can trigger deserialization of untrusted data.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial
ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in remote code execution in the context of the vulnerable Camel application, provided a usable deserialization gadget chain is present on the application classpath. Because exploitation occurs during message consumption, an attacker with the ability to publish to a consumed queue or topic may be able to execute arbitrary code, compromise the application process, access or modify application data, pivot within the environment, or disrupt service availability depending on the privileges and environment of the Camel runtime.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, reduce exposure by preventing untrusted parties from publishing JMS ObjectMessage payloads to queues or topics consumed by Camel, disabling or avoiding ObjectMessage-based workflows where feasible, and reviewing Camel JMS consumer configurations that rely on the default mapJmsMessage behavior. Additional risk reduction can be achieved by limiting reachable gadget chains on the application classpath and enforcing broker- and application-level controls so only trusted producers can send to affected destinations. However, the authoritative fix is to upgrade to a patched Camel version.

Remediation

Patch, then assume compromise.

Upgrade Apache Camel to a fixed release. Apache states the issue is fixed in 4.14.7, 4.18.2, and 4.20.0. Users should upgrade to 4.20.0 where possible; users on the 4.14.x LTS stream should upgrade to 4.14.7, and users on the 4.18.x stream should upgrade to 4.18.2.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationCamelapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

8 SOURCESView more in app
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Start free trial
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2026-40860
NVD
nvd.nist.gov/vuln/detail/CVE-2026-40860
MITRE CWE · CWE-502
Deserialization of Untrusted Data
Vendor Advisory
camel.apache.org/security/CVE-2026-40860.html
Third Party Advisory
openwall.com/lists/oss-security/2026/04/26/10