Affects Apache Camel, a widely used integration framework; enables remote code execution and arbitrary file write via JMS header manipulation, risking disruption of enterprise routing.
CVE-2026-40453
RCE and file write via JMS header manipulation in Camel due to case-sensitive filter bug.
Is CVE-2026-40453 being exploited?
Not confirmed. CVE-2026-40453 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.6% probability of exploitation in the next 30 days.
How severe is CVE-2026-40453?
CVE-2026-40453 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-40453?
Yes. A fix has been recorded for CVE-2026-40453. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-40453 affect?
CVE-2026-40453 affects Apache Camel core, camel-jms, camel-sjms, camel-coap, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-40453?
Upgrade to Camel 4.20.0 (or 4.14.6/4.18.2 for older branches)
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution and arbitrary file write via JMS header variants; attacker with JMS broker access can trigger downstream components.
Patch when possible
- affected>= 3.0.0 and < 4.14.6
- affected>= 4.15.0 and < 4.18.2
- affected>= 4.19.0 and < 4.20.0
- affected>= 3.0.0 and < 4.14.6
- affected>= 4.15.0 and < 4.18.2
- affected>= 4.19.0 and < 4.20.0
- affected>= 3.0.0 and < 4.14.6
- affected>= 4.15.0 and < 4.18.2
- affected>= 4.19.0 and < 4.20.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.