CVE-2026-40860: JmsBinding.extractBodyFromJms() in camel-jms, and the equivalent JmsBinding class in camel-sjms, deserialized

Q: How do I fix CVE-2026-40860?

camel: upgrade to 4.14.7, 4.18.2. Exact commands for each OS are on this page.

Q: Is CVE-2026-40860 being exploited?

CVE-2026-40860 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-40860 affect?

CVE-2026-40860 affects camel. Severity is critical (CVSS 9.8). 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, c

Q: How urgent is CVE-2026-40860?

Priority 67/100. Critical severity; CISA SSVC: automatable with total technical impact; Remotely exploitable, no login, no user action; On your watchlist

This week

CRITICAL 9.8REMOTEWATCHLISTUPGRADE

CVE-2026-40860 is a critical-severity flaw (CVSS 9.8) affecting camel. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 ObjectMessa

Why this priority

Critical severity
CISA SSVC: automatable with total technical impact
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.7% (top 22%)
CISA exploited list	No
Weakness	CWE-502
Published	2026-04-27
Last modified	2026-10-26

Publisher (CNA): Apache Software Foundation · Vendor: apache

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-27 09:16 UTCPublished CVE record published
2026-10-26 22:10 UTCUpdated Record last modified

apache camel UPGRADE

Affected: >= 3.0.0 and < 4.14.7 · >= 4.15.0 and < 4.18.2 · 4.19.0

Fixed in: 4.14.7, 4.18.2

Safe to downgrade to: a release before 3.0.0

1. Check installed version

apt-cache policy camel || rpm -q camel || camel --version

2. UPGRADE to 4.14.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade camel

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade camel

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)

apt-cache madison camel sudo apt install camel=<VERSION_BEFORE_3.0.0> sudo apt-mark hold camel

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list camel sudo dnf downgrade camel-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add camel

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Maven · org.apache.camel:camel-jms · FIXED · 4.14.7 · vulnerable: >= 3.0.0, < 4.14.7 · source

Set org.apache.camel:camel-jms to 4.14.7 or later in pom.xml or build.gradle, then rebuild and redeploy.

Maven · org.apache.camel:camel-sjms · FIXED · 4.14.7 · vulnerable: >= 3.0.0, < 4.14.7 · source

Set org.apache.camel:camel-sjms to 4.14.7 or later in pom.xml or build.gradle, then rebuild and redeploy.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

GitHub PoC: oscerd/CVE-2026-40860 (0 stars)

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-40860?

camel: upgrade to 4.14.7, 4.18.2. Exact commands for each OS are on this page.

Is CVE-2026-40860 being exploited?

CVE-2026-40860 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-40860 affect?

CVE-2026-40860 affects camel. Severity is critical (CVSS 9.8). 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, c

How urgent is CVE-2026-40860?

Priority 67/100. Critical severity; CISA SSVC: automatable with total technical impact; Remotely exploitable, no login, no user action; On your watchlist

Related CVEs

CVE-2026-33453 CRITICAL 10.0 UPGRADE Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Apache Camel C
CVE-2026-33454 CRITICAL 9.4 UPGRADE The Camel-Mail component is vulnerable to Camel message header injection
CVE-2026-40453 CRITICAL 9.9 UPGRADE The fix for CVE-2025-27636 added setLowerCase(true) to HttpHeaderFilterStrategy so that case-variant header na
CVE-2026-40473 HIGH 8.8 UPGRADE The camel-mina component's MinaConverter.toObjectInput(IoBuffer) type converter wraps an IoBuffer in a java.io
CVE-2026-40858 HIGH 8.8 UPGRADE The camel-infinispan component's ProtoStream-based remote aggregation repository deserializes data read from a

References

← Back to latest CVEs