cve.bz

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

7.3 highEPSS 0.7%Fix available

High (7.3) in apache camel. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.camel:camel-jms 4.14.8, 4.18.3, 4.21.0.

On this page
Deserialization of Untrusted Data vulnerability in Apache Camel, Apache Camel JMS component. JmsBinding.extractBodyFromJms() in camel-jms - and the equivalent JmsBinding in camel-sjms - deserializes the payload of an incoming JMS ObjectMessage via jakarta.jms.ObjectMessage.getObject() whenever the mapJmsMessage option is enabled (the default) and Camel acts as a JMS consumer. The CVE-2026-40860 hardening added a post-deserialization class check that rejects classes outside the default allow-list java.**;javax.**;org.apache.camel.**;!*. However org.apache.camel.support.DefaultExchangeHolder itself lives in the allow-listed org.apache.camel.** namespace, so an ObjectMessage whose top-level object is a DefaultExchangeHolder passes the check. The receiving side then calls DefaultExchangeHolder.unmarshal() on it without requiring the transferExchange option to be enabled - an asymmetric trust boundary, since the sending side gates ObjectMessage and transferExchange handling but the receiving side did not - writing every non-null field of the holder into the Exchange: the message body, the IN and OUT headers, the exchange properties, the variables, the exchange id and the exception. An attacker who can publish an ObjectMessage to a queue or topic consumed by an affected Camel application can therefore inject arbitrary Exchange state using only universally-trusted java.lang and java.util types, with no deserialization gadget chain required, to manipulate routing and headers, exchange properties and error handling. The same handling applies to camel-sjms and camel-sjms2, and to the JMS-family components built on JmsComponent and JmsBinding: camel-amqp, camel-activemq and camel-activemq6. This is a bypass of the CVE-2026-40860 fix rather than a flaw in it. This issue affects Apache Camel: from 3.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0; Apache Camel: from 3.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.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.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. After upgrading, JMS ObjectMessage handling is disabled by default in camel-jms, camel-sjms and the JMS-family components (a new objectMessageEnabled option defaults to false at the component and endpoint level), so an incoming ObjectMessage - including a DefaultExchangeHolder payload - is no longer deserialized unless the option is explicitly enabled; only set objectMessageEnabled=true when the consumed JMS destination is fed exclusively by trusted producers. For deployments that cannot upgrade immediately, restrict publish access to the queues and topics consumed by Camel to trusted producers via JMS broker authorization, and do not expose JMS consumers that map ObjectMessage bodies to untrusted networks; a JMS-provider deserialization allow-list does not mitigate this specific bypass because the crafted payload uses only universally-trusted classes.

Severity

CVSS 3.1

7.3 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 52nd 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: partial, assessed 2026-07-06. 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
Record from
the NVD, synced

Fix and patched versions

  • org.apache.camel:camel-jms (Maven): fixed in 4.14.8, 4.18.3, 4.21.0
  • org.apache.camel:camel-sjms (Maven): fixed in 4.14.8, 4.18.3, 4.21.0
  • org.apache.camel:camel-sjms2 (Maven): fixed in 4.14.8, 4.18.3, 4.21.0
  • org.apache.camel:camel-amqp (Maven): fixed in 4.14.8, 4.18.3, 4.21.0
  • org.apache.camel:camel-activemq (Maven): fixed in 4.14.8, 4.18.3, 4.21.0
  • org.apache.camel:camel-activemq6 (Maven): fixed in 4.14.8, 4.18.3, 4.21.0
  • Vendor advisory: https://camel.apache.org/security/CVE-2026-43866.html

Ask an AI about this CVE

Show the promptExplain CVE-2026-43866 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-43866?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-43866?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-43866 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-43866

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-43866](https://cve.bz/cve/badge/CVE-2026-43866.svg)](https://cve.bz/cve/CVE-2026-43866)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 3.0.0 before 4.14.8
Apache Software Foundation Apache Camelfrom 4.15.0 before 4.18.3
Apache Software Foundation Apache Camelfrom 4.19.0 before 4.21.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-jms>=3.0.0 <4.14.84.14.8
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-jms>=4.15.0 <4.18.34.18.3
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-jms>=4.19.0 <4.21.04.21.0
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-sjms>=3.0.0 <4.14.84.14.8
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-sjms>=4.15.0 <4.18.34.18.3
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-sjms>=4.19.0 <4.21.04.21.0
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-sjms2>=3.0.0 <4.14.84.14.8
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-sjms2>=4.15.0 <4.18.34.18.3
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-sjms2>=4.19.0 <4.21.04.21.0
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-amqp>=3.0.0 <4.14.84.14.8
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-amqp>=4.15.0 <4.18.34.18.3
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-amqp>=4.19.0 <4.21.04.21.0
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-activemq>=3.0.0 <4.14.84.14.8
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-activemq>=4.15.0 <4.18.34.18.3
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-activemq>=4.19.0 <4.21.04.21.0
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-activemq6>=3.0.0 <4.14.84.14.8
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-activemq6>=4.15.0 <4.18.34.18.3
GHSA-f755-xp6r-8q84Mavenorg.apache.camel:camel-activemq6>=4.19.0 <4.21.04.21.0

Red Hat

Red Hat rates this Important.

Red Hat's statement

A flaw was found in the Apache Camel JMS components. The JmsBinding.extractBodyFromJms() method deserializes incoming JMS ObjectMessage payloads when the mapJmsMessage option is enabled (the default). The prior fix for CVE-2026-40860 can be bypassed using a crafted ObjectMessage containing a DefaultExchangeHolder, which resides within the allowed org.apache.camel namespace. Once deserialized, it injects arbitrary Exchange state including message body, headers, and properties without requiring any deserialization gadget chain. Red Hat builds of Apache Camel for Spring Boot and Quarkus ship the affected camel-jms and camel-amqp components.

Red Hat's mitigation

Restrict publish access to JMS queues and topics consumed by Camel applications via broker authorization. Note that a JMS-provider deserialization allow-list does not mitigate this specific bypass because the crafted payload uses only universally-trusted classes within the org.apache.camel namespace.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4.18.3 for Spring Boot 3.5.16camel-jmsFixed 2026-08-13RHSA-2026:54622
Red Hat build of Apache Camel 4 for Quarkus 3camel-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-43866.

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-43866 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-43866 — Apache Camel camel-jms forged DefaultExchangeHolder bypass of the CVE-2026-40860 deserialization filter (Ex…

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