BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-40860High confidence

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

Apache Software Foundation · Apache Camel

9.8CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 1.53% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Apache Software Foundation Apache Camel and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Open-source package ranges36 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenorg.apache.camel:camel-activemqECOSYSTEM: introduced 3.0.0; fixed 4.14.74.14.7OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-activemqECOSYSTEM: introduced 4.15.0; fixed 4.18.24.18.2OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-activemqECOSYSTEM: introduced 4.19.0; fixed 4.20.04.20.0OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-activemq6ECOSYSTEM: introduced 3.0.0; fixed 4.14.74.14.7OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-activemq6ECOSYSTEM: introduced 4.15.0; fixed 4.18.24.18.2OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-activemq6ECOSYSTEM: introduced 4.19.0; fixed 4.20.04.20.0OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-amqpECOSYSTEM: introduced 3.0.0; fixed 4.14.74.14.7OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-amqpECOSYSTEM: introduced 4.15.0; fixed 4.18.24.18.2OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-amqpECOSYSTEM: introduced 4.19.0; fixed 4.20.04.20.0OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-jmsECOSYSTEM: introduced 3.0.0; fixed 4.14.74.14.7OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-jmsECOSYSTEM: introduced 4.15.0; fixed 4.18.24.18.2OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-jmsECOSYSTEM: introduced 4.19.0; fixed 4.20.04.20.0OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-sjmsECOSYSTEM: introduced 3.0.0; fixed 4.14.74.14.7OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-sjmsECOSYSTEM: introduced 4.15.0; fixed 4.18.24.18.2OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-sjmsECOSYSTEM: introduced 4.19.0; fixed 4.20.04.20.0OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-sjms2ECOSYSTEM: introduced 3.0.0; fixed 4.14.74.14.7OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-sjms2ECOSYSTEM: introduced 4.15.0; fixed 4.18.24.18.2OSV record ↗aggregator derived · 26 Aug 2026
Mavenorg.apache.camel:camel-sjms2ECOSYSTEM: introduced 4.19.0; fixed 4.20.04.20.0OSV record ↗aggregator derived · 26 Aug 2026
mavenorg.apache.camel:camel-activemq>= 3.0.0, < 4.14.74.14.7GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-activemq>= 4.15.0, < 4.18.24.18.2GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-activemq>= 4.19.0, < 4.20.04.20.0GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-activemq6>= 3.0.0, < 4.14.74.14.7GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-activemq6>= 4.15.0, < 4.18.24.18.2GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-activemq6>= 4.19.0, < 4.20.04.20.0GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-amqp>= 3.0.0, < 4.14.74.14.7GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-amqp>= 4.15.0, < 4.18.24.18.2GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-amqp>= 4.19.0, < 4.20.04.20.0GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-jms>= 3.0.0, < 4.14.74.14.7GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-jms>= 4.15.0, < 4.18.24.18.2GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-jms>= 4.19.0, < 4.20.04.20.0GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-sjms>= 3.0.0, < 4.14.74.14.7GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-sjms>= 4.15.0, < 4.18.24.18.2GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-sjms>= 4.19.0, < 4.20.04.20.0GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-sjms2>= 3.0.0, < 4.14.74.14.7GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-sjms2>= 4.15.0, < 4.18.24.18.2GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
mavenorg.apache.camel:camel-sjms2>= 4.19.0, < 4.20.04.20.0GitHub advisory ↗github reviewed aggregator · 26 Aug 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-40860 · CSAF 2.0 · revision 3 · finalRed Hat Product SecurityApache Camel: camel-jms: camel-sjms: camel-sjms2: camel-amqp: camel-activemq: camel-activemq6: Apache Camel: Remote Code Execution via deserialization of JMS ObjectMessage
2 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • camel-amqp as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • camel-jms as a component of Red Hat build of Apache Camel 4 for Quarkus 3
Summary
A flaw was found in Apache Camel. A remote attacker could exploit a deserialization vulnerability by sending a specially crafted Java Message Service (JMS) ObjectMessage to a Camel application acting as a JMS consumer. This vulnerability arises because the application deserializes the message payload without proper validation. Successful exploitation could lead to remote code execution on the system consuming the message, provided a deserialization gadget chain is present on the classpath.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-25794

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
9.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

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.

What

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.

Why

Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

What

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.

Why

Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Deserialization of Untrusted Data → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-502 ↗

CWE-502: Deserialization of Untrusted Data. The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code executionCWE-502
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-25794Official EUVD mapping

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.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2308SAP Patch Day Juli 2026

Ein Angreifer kann mehrere Schwachstellen in SAP Software ausnutzen, um Dateien zu manipulieren, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um einen SQL-Injection Angriff durchzuführen, um einen Cross-Site Scripting Angriff durchzuführen, um Sicherheitsvorkehrungen zu umgehen, und um beliebigen Programmcode auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-1271Apache Camel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Apache Camel ausnutzen, um beliebigen Programmcode auszuführen, Daten zu manipulieren oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260429Security Bulletin 29 Apr 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Apr 2026, published on 29 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0877Multiples vulnérabilités dans les produits SAP

illet 2026 https://support.sap.com/en/my-support/knowledge-base/security-notes-news/july-2026.html Référence CVE CVE-2025-68161 https://www.cve.org/CVERecord?id=CVE-2025-68161 Référence CVE CVE-2026-0487 https://www.cve.org/CVERecord?id=CVE-2026-0487 Référence CVE CVE-2026-24315 https://www.cve.org/CVERecord?id=CVE-2026-24315 Référence CVE CVE-2026-27690 https://www.cve.org/CVERecord?id=CVE-2026-27690 Référence CVE CVE-2026-33454 https://www.cve.org/CVERecord?id=CVE-2026-33454 Référence CVE CVE-2026-40128 https://www.cve.org/CVERecord?id=CVE-2026-40128 Référence CVE CVE-2026-40453 https://www.cve.org/CVERecord?id=CVE-2026-40453 Référence CVE CVE-2026-40860 https://www.cve.org/CVERecord?id=CVE-2026-40860 Référence CVE CVE-2026-41293 https://www.cve.org/CVERecord?id=CVE-2026-41293 Référence CVE CVE-2026-43512 https://www.cve.org/CVERecord?id=CVE-2026-43512 Référence CVE CVE-2026-43515 https://www.cve.org/CVERecord?id=CVE-2026-43515 Référence CVE CVE-2026-44745 https://www.cve.org/CVERecord?id=CVE-2026-44745 Référence CVE CVE-2026-44747 https://www.cve.org/CVERecord?id=CVE-2026-44747 Référence CVE CVE-2026-44752 https://www.cve.org/CVERecord?id=CVE-2026-44752 Référence CVE CVE-2026-44753 https://www.cve.org/CVERecord?id=CVE-2026-44753 Référence CVE CVE-2026-44759 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-013161Apache Software FoundationのApache Camelにおける信頼できないデータのデシリアライゼーションに関する脆弱性

camel-jms の JmsBinding.extractBodyFromJms() および camel-sjms の同等の JmsBinding クラスは、javax.jms.ObjectMessage.getObject() を介して受信した JMS ObjectMessage のペイロードをデシリアライズする際に、ObjectInputFilter やクラスの許可リスト・拒否リストを適用していませんでした。このコードパスは mapJmsMessage オプションが有効（デフォルト設定）で Camel が JMS コンシューマとして動作する場合に常に到達します。そのため、悪意のある ObjectMessage を Camel アプリケーションが消費するキューやトピックに送信できる攻撃者は、クラスパスにデシリアライズガジェットチェーンが存在する場合、リモートコード実行を達成する可能性がありました。同様の処理は、camel-sjms2（Sjms2Endpoint が SjmsEndpoint を拡張）、camel-amqp（AMQPJmsBinding が JmsBinding を拡張）、および JmsComponent 上に構築された他の JMS ファミリーコンポーネント（camel-activemq、camel-activemq6）を通じても間接的に達成されました。この問題は Apache Camel のバージョン 3.0.0 から 4.14.7 より前、4.15.0 から 4.18.2 より前、4.19.0 から 4.20.0 より前に影響します。ユーザーはこの問題を修正したバージョン 4.20.0 へアップグレードすることを推奨します。4.14.x LTS リリースストリームを使用している場合は 4.14.7 へ、4.18.x リリースストリームを使用している場合は 4.18.2 へのアップグレードを推奨します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-022929Apache Software FoundationのApache Camelにおける信頼できないデータのデシリアライゼーションに関する脆弱性

Apache CamelおよびApache Camel JMSコンポーネントにおける信頼されていないデータのデシリアライズ脆弱性です。camel-jmsのJmsBinding.extractBodyFromJms()および同等のcamel-sjms内のJmsBindingは、mapJmsMessageオプションが有効（デフォルト）かつCamelがJMSコンシューマとして動作している場合に、受信したJMS ObjectMessageのペイロードをjakarta.jms.ObjectMessage.getObject()を通じてデシリアライズします。CVE-2026-40860の強化により、デシリアライズ後にクラスチェックが追加され、デフォルトの許可リスト java.**;javax.**;org.apache.camel.**;!* に含まれないクラスは拒否されます。しかし、org.apache.camel.support.DefaultExchangeHolder自体は許可リストに含まれるorg.apache.camel.**名前空間に存在するため、トップレベルのオブジェクトがDefaultExchangeHolderであるObjectMessageはこのチェックを通過します。受信側はtransferExchangeオプションの有効化を要求せずにDefaultExchangeHolder.unmarshal()を呼び出すため（非対称な信頼境界となっており、送信側はObjectMessageとtransferExchange処理を制御しているものの受信側はしていません）、保持者のすべての非nullフィールドをExchangeに書き込みます：メッセージボディ、INおよびOUTヘッダー、Exchangeのプロパティ、変数、Exchange ID、および例外です。攻撃者は影響を受けるCamelアプリケーションで消費されるキューやトピックにObjectMessageを送信できれば、任意のExchange状態をjava.langおよびjava.utilの普遍的に信頼された型のみを用いて（デシリアライズのガジェットチェーン不要で）注入し、ルーティング・ヘッダー、Exchangeプロパティ、エラー処理を操作できます。同様の取り扱いはcamel-sjms、camel-sjms2、およびJmsComponentとJmsBindingに基づくJMS系コンポーネント（camel-amqp、camel-activemq、camel-activemq6）にも適用されます。これはCVE-2026-40860の修正の回避であり、その欠陥ではありません。影響範囲はApache Camelのバージョン3.0.0から4.14.8未満、4.15.0から4.18.3未満、4.19.0から4.21.0未満です。ユーザーはこの問題を修正したバージョン4.21.0へのアップグレードを推奨します。4.14.xのLTSリリースを使用している場合は4.14.8へ、4.18.xのリリースを使用している場合は4.18.3へのアップグレードを推奨します。アップグレード後、camel-jms、camel-sjms、およびJMS系コンポーネントではJMS ObjectMessageの取り扱いはデフォルトで無効化されます（objectMessageEnabledという新しいオプションがコンポーネントおよびエンドポイントレベルでデフォルトfalseです）。したがって、DefaultExchangeHolderペイロードを含む受信ObjectMessageは、明示的にオプションを有効にしない限りデシリアライズされません。objectMessageEnabled=trueは、消費しているJMSデスティネーションが信頼されたプロデューサーのみから供給されている場合にのみ設定してください。すぐにアップグレードできない場合は、JMSブローカーの認可を用いてCamelが消費するキューやトピックへのパブリッシュアクセスを信頼できるプロデューサーに制限し、ObjectMessageボディをマッピングするJMSコンシューマを信頼されていないネットワークに公開しないことを推奨します。なお、JMSプロバイダーのデシリアライズ許可リストでは本特定の回避を軽減できません。なぜなら、悪意あるペイロードは普遍的に信頼されたクラスのみを使用しているためです。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0230Kwetsbaarheden verholpen in SAP-producten

Apache Camel's JMS components contain deserialization vulnerabilities allowing remote code execution via crafted ObjectMessages, affecting multiple versions including those used in SAP Integration Suite's Edge Integration Cell.

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0129Kwetsbaarheden verholpen in Apache Camel

A deserialization vulnerability in Apache Camel's JMS components enables remote code execution via crafted ObjectMessage payloads, affecting versions 3.0.0 to before 4.14.7, 4.15.0 to before 4.18.2, and 4.19.0 to before 4.20.0, with fixes in 4.14.7, 4.18.2, and 4.20.0.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14
Action
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 27 Apr 2026 · Last source change 10 Sept 2026, 12:04 UTC · CWE-502 · Deserialization of Untrusted Data

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-25794
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-40860 to remediation: access.redhat.com/CVE-2026-40860.
    Before
    remediation: access.redhat.com/CVE-2026-40860
    After
    remediation: access.redhat.com/CVE-2026-40860
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    camel-amqp as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-jms as a component of Red Hat build of Apache Camel 4 for Quarkus 3 · Fixed: Red Hat Build of Apache Camel 4.18 for Quarkus 3.33; Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14
    After
    camel-amqp as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-jms as a component of Red Hat build of Apache Camel 4 for Quarkus 3 · Fixed: Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added remediation: camel.apache.org/CVE-2026-40860.html.
    Before
    vendor advisory: camel.apache.org/CVE-2026-40860.html
    After
    remediation: camel.apache.org/CVE-2026-40860.html · vendor advisory: camel.apache.org/CVE-2026-40860.html
    security@apache.org ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    3.0.0 < 4.14.7; 4.15.0 < 4.18.2; 4.19.0 < 4.20.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    Apache Camel: 3.0.0 < 4.14.7, 4.15.0 < 4.18.2, 4.19.0 < 4.20.0 · Fixed: RHSA-2026:22453: Red Hat Build of Apache Camel 4.18 for Quarkus 3.33
    CNA ↗
  5. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    security@apache.org ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-25794↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-40860 · cve.blacktree.nl