CVE-2026-43865
Deserialization in Camel Hazelcast enables RCE.
Is CVE-2026-43865 being exploited?
Not confirmed. CVE-2026-43865 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 0.98% probability of exploitation in the next 30 days.
How severe is CVE-2026-43865?
CVE-2026-43865 is rated High with a CVSS score of 8.1. 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-43865?
Yes. A fix has been recorded for CVE-2026-43865. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-43865 affect?
CVE-2026-43865 affects Apache Camel Hazelcast component (default config), Camel routes using hazelcast-consumer/queue/map/etc., HazelcastAggregationRepository, HazelcastIdempotentRepository. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-43865?
Upgrade to Camel 4.21.0; enable Hazelcast deserialization filter if upgrade isn't feasible
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via crafted serialized objects deserialized by Hazelcast in Camel; default config allows unfiltered Java deserialization.
Patch when possible
- affected>= 4.0.0 and < 4.14.8
- affected>= 4.15.0 and < 4.18.3
- affected>= 4.19.0 and < 4.21.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.