8.1

CVE-2026-43865: apache software foundation apache camel Deserialization of Untrusted Data

CVSS: 8.1v3.1HighAnalyzed
AliasesGHSA-xww8-mxqw-m84w
Published 06-07-2026Last modified 06-07-2026

Vulnerability summary

CVE-2026-43865 is a high (CVSS 8.1) Deserialization of Untrusted Data vulnerability in apache software foundation apache camel. EPSS estimates a 0.98% chance of exploitation in the next 30 days, higher than 61.7% of scored vulnerabilities.

Overall risk
33/100
0100
Medium · default modelHow is this calculated?
CVSS score
8.1/10
010
High · v3.1 (CVE.org)
EPSS score
0.98%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Timeline

  1. 06-07-2026
    PublishedVulnerability first disclosed.
  2. 06-07-2026
    Last modifiedVulnerability information updated.

Description

Deserialization of Untrusted Data vulnerability in Apache Camel Hazelcast component. The camel-hazelcast component creates and manages Hazelcast instances using a default configuration that applies no Java deserialization filter. When Camel builds the Hazelcast Config itself - that is, when no user-supplied HazelcastInstance, hazelcastConfigUri, or referenced Config bean is provided - neither Hazelcast's JavaSerializationFilterConfig nor a Camel-side ObjectInputFilter is configured, so objects received over the Hazelcast cluster protocol are deserialized inside Hazelcast's own serialization layer (ObjectInputStream.readObject) before Camel ever processes them. An attacker who can join or otherwise reach the Hazelcast cluster can publish a crafted serialized Java object that is then deserialized on every Camel node, resulting in remote code execution. The exposure is present by default and requires no opt-in endpoint configuration: any route using a hazelcast consumer (hazelcast-topic, hazelcast-queue, hazelcast-seda, hazelcast-map, hazelcast-multimap, hazelcast-replicatedmap, hazelcast-list, hazelcast-set), as well as the HazelcastAggregationRepository and HazelcastIdempotentRepository, is affected whenever the managed instance is created from Camel's default configuration. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.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.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix makes Camel apply a default Hazelcast JavaSerializationFilterConfig (whitelisting the java., javax. and org.apache.camel. class-name prefixes and blacklisting java.net.) to instances it creates from its own default configuration, while leaving any user-supplied Config or HazelcastInstance untouched. For deployments that cannot upgrade immediately, configure a deserialization filter on the Hazelcast instance (Hazelcast JavaSerializationFilterConfig, or the JVM-wide system property -Djdk.serialFilter=!java.net.**;java.**;javax.**;org.apache.camel.**;!*) and enable Hazelcast cluster authentication and TLS to restrict who can reach the cluster.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.98%

Chance of exploitation in the next 30 days

Percentile

62%

Versus all other CVEs

30-day change

0.00 pp

From 0.98% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.98%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Apache1 product
  • camel≥ 4.0.0, < 4.14.8 | ≥ 4.15.0, < 4.18.3 | ≥ 4.19.0, < 4.21.0
Apache software foundation1 product
  • apache camel≥ 4.0.0, < 4.14.8 | ≥ 4.15.0, < 4.18.3 | ≥ 4.19.0, < 4.21.0
Org.apache.camel1 product
  • camel-hazelcast≥ 4.0.0, < 4.14.8 | ≥ 4.15.0, < 4.18.3 | ≥ 4.19.0, < 4.21.0

3 vendors · 3 products

References

14 links
Show all 14 references