CVE-2026-40860: Apache Camel: Unsafe Deserialization of JMS ObjectMessage in camel-jms, camel-sjms, camel-sjms2 and camel-amqp
Noroxi assessment
Priority: Plan (action score 40/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.7% (FIRST EPSS); higher than 78% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Apache Software Foundation Apache Camel 4.14.7, 4.18.2, 4.20.0.
Add it to your regular patch cycle. Upgrade to Apache Software Foundation Apache Camel 4.14.7, 4.18.2, 4.20.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 27, 2026
- Updated
- Oct 26, 2026
- EPSS
- 1.7% · 78th percentile
- CWE
- CWE-502
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| apache | camel | cpe:2.3:a:apache:camel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Software Foundation Apache Camel
- 3.0.0 and later · before 4.14.7affected · semver
- 4.15.0 and later · before 4.18.2affected · semver
- 4.19.0 and later · before 4.20.0affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache camel3.0.0 and later · before 4.14.7
- apache camel4.15.0 and later · before 4.18.2
- apache camel4.19.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.apache.camel:camel-activemq | from 3.0.0 · before 4.14.7 | 4.14.7 |
| Maven | org.apache.camel:camel-activemq | from 4.15.0 · before 4.18.2 | 4.18.2 |
| Maven | org.apache.camel:camel-activemq | from 4.19.0 · before 4.20.0 | 4.20.0 |
| Maven | org.apache.camel:camel-activemq6 | from 3.0.0 · before 4.14.7 | 4.14.7 |
| Maven | org.apache.camel:camel-activemq6 | from 4.15.0 · before 4.18.2 | 4.18.2 |
| Maven | org.apache.camel:camel-activemq6 | from 4.19.0 · before 4.20.0 | 4.20.0 |
| Maven | org.apache.camel:camel-amqp | from 3.0.0 · before 4.14.7 | 4.14.7 |
| Maven | org.apache.camel:camel-amqp | from 4.15.0 · before 4.18.2 | 4.18.2 |
| Maven | org.apache.camel:camel-amqp | from 4.19.0 · before 4.20.0 | 4.20.0 |
| Maven | org.apache.camel:camel-jms | from 3.0.0 · before 4.14.7 | 4.14.7 |
| Maven | org.apache.camel:camel-jms | from 4.15.0 · before 4.18.2 | 4.18.2 |
| Maven | org.apache.camel:camel-jms | from 4.19.0 · before 4.20.0 | 4.20.0 |
| Maven | org.apache.camel:camel-sjms | from 3.0.0 · before 4.14.7 | 4.14.7 |
| Maven | org.apache.camel:camel-sjms | from 4.15.0 · before 4.18.2 | 4.18.2 |
| Maven | org.apache.camel:camel-sjms | from 4.19.0 · before 4.20.0 | 4.20.0 |
| Maven | org.apache.camel:camel-sjms2 | from 3.0.0 · before 4.14.7 | 4.14.7 |
| Maven | org.apache.camel:camel-sjms2 | from 4.15.0 · before 4.18.2 | 4.18.2 |
| Maven | org.apache.camel:camel-sjms2 | from 4.19.0 · before 4.20.0 | 4.20.0 |
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-27636Apache Camel: Camel Message Header Injection via Improper Filtering51Plan
- CVE-2026-47323Apache Camel: Camel-CXF Message Header Injection via Missing Inbound Filtering45Plan
- CVE-2026-33453Apache Camel: CoAP URI Query Parameter to Exchange Header Injection in camel-coap Allows Single-Packet Pre-Auth Remote Code Execution43Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-40453Apr 27, 2026 · Apache Camel JMS, Apache Camel CoAP, Apache Camel Google PubSub: Incomplete fix for CVE-2025-27636 in non-HTTP HeaderFilterStrategies (camel-jms, camel-sjms…40Plan
- ← EarlierCVE-2026-40473Apr 27, 2026 · Apache Camel Mina: Unsafe Deserialization in MinaConverter.toObjectInput() via TCP/UDP35Monitor
- Later →CVE-2026-33454Apr 27, 2026 · Apache Camel: Inbound Header Filter Missing in MailHeaderFilterStrategy Allows Remote Code Execution via MIME Header Injection (CVE-2025-30177 Variant)37Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Apache Software Foundation Apache Camel | 4.14.7 | Vendor (CNA) |
| Apache Software Foundation Apache Camel | 4.18.2 | Vendor (CNA) |
| Apache Software Foundation Apache Camel | 4.20.0 | Vendor (CNA) |
| Maven:org.apache.camel:camel-activemq | 4.14.7 | Package registry (OSV) |
| Maven:org.apache.camel:camel-activemq | 4.18.2 | Package registry (OSV) |
| Maven:org.apache.camel:camel-activemq | 4.20.0 | Package registry (OSV) |
| Maven:org.apache.camel:camel-activemq6 | 4.14.7 | Package registry (OSV) |
| Maven:org.apache.camel:camel-activemq6 | 4.18.2 | Package registry (OSV) |
| Maven:org.apache.camel:camel-activemq6 | 4.20.0 | Package registry (OSV) |
| Maven:org.apache.camel:camel-amqp | 4.14.7 | Package registry (OSV) |
| Maven:org.apache.camel:camel-amqp | 4.18.2 | Package registry (OSV) |
| Maven:org.apache.camel:camel-amqp | 4.20.0 | Package registry (OSV) |
| Maven:org.apache.camel:camel-jms | 4.14.7 | Package registry (OSV) |
| Maven:org.apache.camel:camel-jms | 4.18.2 | Package registry (OSV) |
| Maven:org.apache.camel:camel-jms | 4.20.0 | Package registry (OSV) |
| Maven:org.apache.camel:camel-sjms | 4.14.7 | Package registry (OSV) |
| Maven:org.apache.camel:camel-sjms | 4.18.2 | Package registry (OSV) |
| Maven:org.apache.camel:camel-sjms | 4.20.0 | Package registry (OSV) |
| Maven:org.apache.camel:camel-sjms2 | 4.14.7 | Package registry (OSV) |
| Maven:org.apache.camel:camel-sjms2 | 4.18.2 | Package registry (OSV) |
| Maven:org.apache.camel:camel-sjms2 | 4.20.0 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-07-10 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+74 d
- TodayNov 16, 2026+203 d
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Venkatraman KumarSecurinfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-78162175 days apartApache Camel: Camel-Hazelcast Managed Instances Missing Java Deserialization Filter (Incomplete Fix for CVE-2026-43865)40Plan
- CVE-2026-4386770 days apartApache Camel: Camel-PQC: The AWS Secrets Manager key-lifecycle manager deserializes persisted key metadata with java.io.ObjectInputStream and no…39Monitor
- CVE-2026-334540 days apartApache Camel: Inbound Header Filter Missing in MailHeaderFilterStrategy Allows Remote Code Execution via MIME Header Injection (CVE-2025-30177 Variant)37Monitor
- CVE-2026-271720 days apartApache Camel: Unsafe Java deserialization in camel-consul ConsulRegistry allows arbitrary code execution via malicious values read from the Consul KV store35Monitor
- CVE-2026-404730 days apartApache Camel Mina: Unsafe Deserialization in MinaConverter.toObjectInput() via TCP/UDP35Monitor
- CVE-2026-408580 days apartApache Camel: Camel-Infinispan: Unsafe Deserialization in Remote Aggregation Repository35Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-502 · Deserialization of Untrusted DataCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.
The bug in code
The whole CWE-502 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
payload = sock.recv(65536)
job = pickle.loads(payload)Fixed
payload = sock.recv(65536)
if not hmac.compare_digest(sign(payload), header_sig):
raise PermissionError("invalid signature")
job = JobSchema.validate(json.loads(payload))Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.