cve.bz

CVE-2026-40860 apache camel: Deserialization of Untrusted Data

9.8 criticalEPSS 1.7%Fix available

Critical (9.8) in apache camel. EPSS 1.7% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.camel:camel-jms 4.14.7, 4.18.2, 4.20.0.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
1.7% (unchanged from 1.7% a week ago; 1.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 78th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-04-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • org.apache.camel:camel-jms (Maven): fixed in 4.14.7, 4.18.2, 4.20.0
  • org.apache.camel:camel-sjms (Maven): fixed in 4.14.7, 4.18.2, 4.20.0
  • org.apache.camel:camel-sjms2 (Maven): fixed in 4.14.7, 4.18.2, 4.20.0
  • org.apache.camel:camel-amqp (Maven): fixed in 4.14.7, 4.18.2, 4.20.0
  • org.apache.camel:camel-activemq (Maven): fixed in 4.14.7, 4.18.2, 4.20.0
  • org.apache.camel:camel-activemq6 (Maven): fixed in 4.14.7, 4.18.2, 4.20.0
  • Vendor advisory: https://camel.apache.org/security/CVE-2026-40860.html

Ask an AI about this CVE

Show the promptExplain CVE-2026-40860 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40860?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40860?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-40860 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-40860

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-40860](https://cve.bz/cve/badge/CVE-2026-40860.svg)](https://cve.bz/cve/CVE-2026-40860)

HTML:

<a href="https://cve.bz/cve/CVE-2026-40860"><img src="https://cve.bz/cve/badge/CVE-2026-40860.svg" alt="CVE-2026-40860"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 3.0.0 before 4.14.7
Apache Software Foundation Apache Camelfrom 4.15.0 before 4.18.2
Apache Software Foundation Apache Camelfrom 4.19.0 before 4.20.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-jms>=3.0.0 <4.14.74.14.7
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-jms>=4.15.0 <4.18.24.18.2
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-jms>=4.19.0 <4.20.04.20.0
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-sjms>=3.0.0 <4.14.74.14.7
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-sjms>=4.15.0 <4.18.24.18.2
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-sjms>=4.19.0 <4.20.04.20.0
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-sjms2>=3.0.0 <4.14.74.14.7
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-sjms2>=4.15.0 <4.18.24.18.2
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-sjms2>=4.19.0 <4.20.04.20.0
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-amqp>=3.0.0 <4.14.74.14.7
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-amqp>=4.15.0 <4.18.24.18.2
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-amqp>=4.19.0 <4.20.04.20.0
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-activemq>=3.0.0 <4.14.74.14.7
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-activemq>=4.15.0 <4.18.24.18.2
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-activemq>=4.19.0 <4.20.04.20.0
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-activemq6>=3.0.0 <4.14.74.14.7
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-activemq6>=4.15.0 <4.18.24.18.2
GHSA-m5vh-3fw5-5wghMavenorg.apache.camel:camel-activemq6>=4.19.0 <4.20.04.20.0

Red Hat

Red Hat rates this Important.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14camel-amqpFixed 2026-05-14RHSA-2026:17668
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14camel-jmsFixed 2026-05-14RHSA-2026:17668
Red Hat Build of Apache Camel 4.18 for Quarkus 3.33camel-amqpFixed 2026-06-02RHSA-2026:22453
Red Hat Build of Apache Camel 4.18 for Quarkus 3.33camel-jmsFixed 2026-06-02RHSA-2026:22453
Red Hat build of Apache Camel 4 for Quarkus 3camel-amqpAffected
Red Hat build of Apache Camel 4 for Quarkus 3camel-jmsAffected
Red Hat Fuse 7camel-amqpNot affected
Red Hat Fuse 7camel-jmsNot affected
Red Hat Fuse 7camel-jms-starterNot affected
Red Hat JBoss Enterprise Application Platform 8camel-amqpNot affected
Red Hat JBoss Enterprise Application Platform 8camel-jmsNot affected
Red Hat JBoss Enterprise Application Platform Expansion Packcamel-amqpNot affected
Red Hat JBoss Enterprise Application Platform Expansion Packcamel-jmsNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-40860.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • oscerd/CVE-2026-40860 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-40860 — Apache Camel camel-jms/sjms/amqp JMS ObjectMessage unsafe deserialization (RCE)

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON