Home › Vulnerabilities

Apache Software Foundation Apache Camel Flaw CVE-2026-78162: Update Now

Published November 8, 2026 · Last updated November 8, 2026

Apache CVE Critical Patch

The short version: CVE-2026-78162 is a critical-severity security flaw in Apache Software Foundation Apache Camel. The National Vulnerability Database (NVD) published it on October 19, 2026, and the score it lists is 9.8 out of 10. When FraudMeNot checked on November 8, 2026, CISA had not added CVE-2026-78162 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-78162

The record was filed by apache.org. In its own words: "Deserialization of Untrusted Data vulnerability in Apache Camel. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. The camel-hazelcast component applies a default Hazelcast JavaSerializationFilterConfig to the instances it creates from its own configuration, a protection introduced by CVE-2026-43865. That change did not reach two of the configuration paths Camel builds itself, so those paths continued to create Hazelcast instances whose Java deserialization is unrestricted. ReplicatedHazelcastAggregationRepository extends HazelcastAggregationRepository but overrides doStart() without calling super.doStart(), keeping its own copy of the bootstrap block, and therefore never received the filter: a route using it without supplying a hazelcastInstance starts a Hazelcast member that deserializes values read from the backing ReplicatedMap with no class restriction. HazelcastDefaultComponent#getOrCreateHzClientInstance() builds its own ClientConfig when hazelcastMode=client is selected and neither a referenced ClientConfig nor hazelcastConfigUri is supplied, and likewise applied no filter, so client-mode endpoints behaved differently from node-mode endpoints for an otherwise identical configuration. In both cases an attacker able to publish into the Hazelcast cluster that the affected instance is attached to can cause a serialized Java object of their choosing to be deserialized inside Hazelcast's own serialization layer, before Camel processes the exchange, resulting in remote code execution."

Why Apache Camel admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on nist.gov rated CVE-2026-78162 9.8 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Apache Camel running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Scores can differ between the vendor and NVD because each judges the worst realistic case differently. For this flaw, the address listed on apache.org gives it 10.0 (Critical, CVSS 4.0).

Affected Apache Camel releases

According to the record, these releases are vulnerable:

  • 4.0.0 up to, but not including, 4.18.5
  • 4.19.0 up to, but not including, 4.22.1

The type of bug behind CVE-2026-78162

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-502, Deserialization of Untrusted Data. MITRE describes this class of bug as follows: "The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid."

Vendor remediation for CVE-2026-78162

The vendor advisory remediation for operators of Apache Camel, quoted for this page, is: "Upgrade Apache Camel to 4.23.0, 4.22.1 or 4.18.5 (Apache advisory CVE-2026-78162); teams on end-of-life branches should move to a supported branch. Severity note: Apache's own advisory rates this issue Medium, even though the Apache CNA's CVSS 4.0 score is 10.0 and NVD's CVSS 3.1 score is 9.8. Exposure depends on setup: it affects two camel-hazelcast configuration paths that missed the deserialization filter added for CVE-2026-43865, and an attacker must be able to publish data into the connected Hazelcast cluster. If you cannot upgrade yet, apply the explicit Hazelcast serialization filter or pass a supplied, filtered Hazelcast instance as Apache documents."

What to do about it

  • Update now: Upgrade Apache Camel to 4.23.0, 4.22.1 or 4.18.5 (Apache advisory CVE-2026-78162); teams on end-of-life branches should move to a supported branch. Severity note: Apache's own advisory rates this issue Medium, even though the Apache CNA's CVSS 4.0 score is 10.0 and NVD's CVSS 3.1 score is 9.8. Exposure depends on setup: it affects two camel-hazelcast configuration paths that missed the deserialization filter added for CVE-2026-43865, and an attacker must be able to publish data into the connected Hazelcast cluster. If you cannot upgrade yet, apply the explicit Hazelcast serialization filter or pass a supplied, filtered Hazelcast instance as Apache documents.
  • Who should act: IT teams, managed service providers, and developers who run or ship Apache Camel. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from Apache Software Foundation (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from October 19, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-78162. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-78162 record details from CISA and NVD

  • Attack complexity for CVE-2026-78162: low
  • CVE-2026-78162 CVSS scope: unchanged
  • NVD sub-scores for CVE-2026-78162: exploitability 3.9, impact 5.9.
  • Who mapped the weakness type: the address listed on apache.org (Secondary)
  • NVD product identifiers (CPE): cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*
  • References in the NVD record: 8 (8 tagged Patch, 6 tagged Issue Tracking, 3 tagged Vendor Advisory).
  • CISA SSVC decision points for CVE-2026-78162 (from NVD): exploitation=poc; automatable=yes; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).

Dates to know

  • October 19, 2026: NVD publishes CVE-2026-78162.
  • November 8, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-78162 is not listed.
  • November 3, 2026: most recent NVD update (record status: Analyzed).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.