{"answers":{"affected":"6 open source packages ship an affected version, including org.apache.camel:camel-hazelcast. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-43865 in the wild and no public exploit code.","fix":"Upgrade org.apache.camel:camel-hazelcast to a fixed version for your release line: 4.14.8, 4.18.3 or 4.21.0.","what":"CVE-2026-43865 is a high-severity unsafe deserialization vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-43865 and fix it if it is affected.\n\nWhat it is: CVE-2026-43865 is a high-severity unsafe deserialization vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-43865 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.camel:camel-hazelcast (Maven): affected from 4.0.0; fixed in 4.14.8\n- org.apache.camel:camel-hazelcast (Maven): affected from 4.0.0; fixed in 4.14.8\n- org.apache.camel:camel-hazelcast (Maven): affected from 4.15.0; fixed in 4.18.3\n- org.apache.camel:camel-hazelcast (Maven): affected from 4.15.0; fixed in 4.18.3\n- org.apache.camel:camel-hazelcast (Maven): affected from 4.19.0; fixed in 4.21.0\n- org.apache.camel:camel-hazelcast (Maven): affected from 4.19.0; fixed in 4.21.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-43865/ (Markdown: https://insights.sbomify.com/CVE-2026-43865/index.md)","id":"CVE-2026-43865","markdown":"https://insights.sbomify.com/CVE-2026-43865/index.md","name":"CVE-2026-43865","record":{"aliases":["GHSA-xww8-mxqw-m84w"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Camel integration library","requires_auth":"none","summary":"Remote code execution via unsafe Java deserialization in default-configured Apache Camel Hazelcast instances allows attackers to execute arbitrary code.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"camel","vendor":"apache"}],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"Deserialization of Untrusted Data vulnerability in Apache Camel Hazelcast component.\n\nThe 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.\nThis 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.\n\nUsers 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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2026-07-12","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-07-12T09:31:48Z","kind":"github_poc","ref":"https://github.com/oscerd/CVE-2026-43865","stars":0,"title":"Reproducer for CVE-2026-43865 — Apache Camel camel-hazelcast default-configured instance unsafe Java deserialization (RCE)"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Apache Camel-Hazelcast: Unsafe Java deserialization in default-configured managed Hazelcast instances enables remote code execution","id":"CVE-2026-43865","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:camel","products":["apache:camel"],"type":"deserialization","year":"2026"},"n_packages":6,"n_references":1,"next":{"headline":"Apache Camel, Apache Camel: Camel JMS - CVE-2026-40860 fix bypass via DefaultExchangeHolder","id":"CVE-2026-43866"},"packages":[{"ecosystem":"Maven","fixed":["4.14.8"],"introduced":["4.0.0"],"last_affected":[],"package":"org.apache.camel:camel-hazelcast","purl":null,"source":"GHSA-xww8-mxqw-m84w"},{"ecosystem":"Maven","fixed":["4.14.8"],"introduced":["4.0.0"],"last_affected":[],"package":"org.apache.camel:camel-hazelcast","purl":"pkg:maven/org.apache.camel/camel-hazelcast","source":"GHSA-xww8-mxqw-m84w"},{"ecosystem":"Maven","fixed":["4.18.3"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-hazelcast","purl":null,"source":"GHSA-xww8-mxqw-m84w"},{"ecosystem":"Maven","fixed":["4.18.3"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-hazelcast","purl":"pkg:maven/org.apache.camel/camel-hazelcast","source":"GHSA-xww8-mxqw-m84w"},{"ecosystem":"Maven","fixed":["4.21.0"],"introduced":["4.19.0"],"last_affected":[],"package":"org.apache.camel:camel-hazelcast","purl":null,"source":"GHSA-xww8-mxqw-m84w"},{"ecosystem":"Maven","fixed":["4.21.0"],"introduced":["4.19.0"],"last_affected":[],"package":"org.apache.camel:camel-hazelcast","purl":"pkg:maven/org.apache.camel/camel-hazelcast","source":"GHSA-xww8-mxqw-m84w"}],"prev":{"headline":"Null dereference in mutt","id":"CVE-2026-43864"},"products":["Apache Camel"],"published":"2026-07-06","related":[{"cvss_score":10,"headline":"Apache camel-coap allows header injection that can lead to remote code execution","id":"CVE-2026-33453","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":9.9,"headline":"Apache Camel has an incomplete fix for CVE-2025-27636","id":"CVE-2026-40453","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":9.8,"headline":"Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod","id":"CVE-2026-80351","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects","id":"CVE-2026-80352","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection","id":"CVE-2026-71300","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.8,"headline":"Apache Camel-Undertow: the endpoint discarded the undertow-specific header filter strategy in favour of the base HTTP one, so the undertow filtering never ran on endpoint-configured routes","id":"CVE-2026-78329","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.8,"headline":"Apache Camel-PQC: The AWS Secrets Manager key-lifecycle manager deserializes persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter","id":"CVE-2026-43867","kev_date_added":null,"published":"2026-07-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-06","vendors":["Apache Software Foundation"]},"summary":"Remote code execution via unsafe Java deserialization in default-configured Apache Camel Hazelcast instances allows attackers to execute arbitrary code.","url":"https://insights.sbomify.com/CVE-2026-43865/"}