dbcve.org
CamelApplication · Apache

CVE-2026-40860

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-27
Fix available
A fix is available. Upgrade to 4.14.7 / 4.18.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Camel JMS components (camel-jms, camel-sjms, camel-amqp, camel-activemq, etc.) deserialize JMS ObjectMessage payloads without any class filtering in JmsBinding.extractBodyFromJMS(). When mapJmsMessage is enabled (default), attackers can send malicious serialized objects achieving RCE if gadget chains exist on the classpath.

MitigationUpgrade to Apache Camel 4.20.0 (or 4.14.7/4.18.2 for LTS streams) to receive the fix. If upgrade is not immediately feasible, disable mapJmsMessage or implement ObjectInputFilter/allowlist as a compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CamelApplication
Affected:>= 3.0.0, < 4.14.7>= 4.15.0, < 4.18.2= 4.19.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Camel version
    Check your project dependencies (pom.xml, build.gradle) or the camel-core JAR manifest for the Apache Camel version number
    Affected if version is >= 3.0.0 and < 4.14.7, OR >= 4.15.0 and < 4.18.2, OR exactly 4.19.0
  2. Verify JMS component usage
    Inspect your codebase for imports or dependencies on camel-jms, camel-sjms, camel-amqp, or camel-activemq packages; review route definitions using JMS consumers (from("jms:..."))
    Affected if any Camel JMS component is used to consume messages
  3. Check mapJmsMessage configuration
    Search configuration files and route definitions for mapJmsMessage setting; if not explicitly set, it defaults to true; check Spring or Blueprint XML configs, or Java DSL with .option("mapJmsMessage", true)
    Affected if mapJmsMessage is not explicitly set to false (defaults to true)
  4. Confirm ObjectMessage deserialization path
    Review routes that consume JMS messages and verify the JMS message type being processed; if ObjectMessage payloads are expected or possible and mapJmsMessage is enabled, the deserialization path exists
    Affected if ObjectMessage payloads are processed with mapJmsMessage enabled (default)

You are affected if your Apache Camel version falls within the vulnerable ranges AND you use any Camel JMS component with the default mapJmsMessage setting enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.14.7 / 4.18.2 or later
Fixed in 4.14.74.18.2
Interim mitigation

Upgrade to Apache Camel 4.20.0 (or 4.14.7/4.18.2 for LTS streams) to receive the fix. If upgrade is not immediately feasible, disable mapJmsMessage or implement ObjectInputFilter/allowlist as a compensating control.

Recommended fix High confidence

4.20.0 (or 4.14.7 for 4.14.x LTS, or 4.18.2 for 4.18.x)

  1. Identify the current Apache Camel version in use by checking your project's pom.xml or dependencies
  2. Determine which JMS components are in use (camel-jms, camel-sjms, camel-sjms2, camel-amqp, camel-activemq, camel-activemq6)
  3. For Camel 3.0.0 to 4.14.x: Upgrade to version 4.14.7
  4. For Camel 4.15.0 to 4.18.x: Upgrade to version 4.18.2
  5. For Camel 4.19.0: Upgrade to version 4.20.0
  6. After upgrading, verify the application starts successfully and test JMS message consumption functionality
  7. Ensure the classpath does not contain untrusted deserialization gadget chains (e.g., known vulnerable libraries like Apache Commons Collections pre-3.2.2)
Caveat Minor: Review release notes for any behavioral changes between your current version and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Camel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40860 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40860 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data