Threat Intelligence / CVE / CVE-2026-40860

CVE-2026-40860 — Apache Camel

CVSS v3.1 9.8 (CRITICAL) · EPSS 0.8% (higher than 54.9% of all scored CVEs) · Priority 9.1/10 · Published 2026-04-27

As of 2026-06-30, CVE-2026-40860 is a CRITICAL-severity vulnerability in Apache Camel, CVSS v3.1 9.8, EPSS 0.8% (54.9th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-40860, most recently “SAP July 2026 Patch Day: Critical Memory Corruption in NetWeaver ABAP (CVE-2026-44747, CVSS 9.9) Among 16 Security Notes”.

Last updated: 2026-06-30

What is CVE-2026-40860?

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.

The record classifies CVE-2026-40860 under weakness class CWE-502. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 139 days ago.

Severity and exploitation probability

CVSS v3.1 base score
9.8 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (FIRST)
0.8% probability of exploitation in the next 30 days, higher than 54.9% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
9.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-04-27, last modified 2026-06-30

Is CVE-2026-40860 being exploited?

Weaponised exploit code for CVE-2026-40860 is publicly available. 1 public proof-of-concept repository is tracked for this identifier.

Affected products and versions

How to fix CVE-2026-40860

Vendor advisory: https://camel.apache.org/security/CVE-2026-40860.html. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-40860

1 tracked threat in the Threadlinqs corpus references CVE-2026-40860, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Full detection coverage & IOCs for threats exploiting CVE-2026-40860 are available via the Threadlinqs MCP server (Purple tier). View plans →

← all vulnerabilities · Markdown version · Threadlinqs Intelligence