# CVE-2026-27172: camel-consul RCE — Fixed in 4.14.6 ☕ ☕ Maven Not in CISA KEV HIGH severity # CVE-2026-27172 — camel-consul HIGH [Fix: apache/camel#21530](https://github.com/apache/camel/pull/21530) CVE-2026-27172 is a high-severity (CVSS 8.8) Deserialization of Untrusted Data vulnerability in org.apache.camel:camel-consul. A fix is available for org.apache.camel:camel-consul — see the affected versions and patch details below. Apache Camel: Unsafe Java deserialization in camel-consul ConsulRegistry allows arbitrary code execution via malicious values read from the Consul KV store Also known as[GHSA-5rc6-9qfp-8vwg](/vulnerability/GHSA-5rc6-9qfp-8vwg) Published Apr 27, 2026 Updated Oct 28, 2026 Affected 2 pkgs Patched 2 / 2 Exploits None indexed Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - A successful exploit gives an attacker total control of the affected component, not partial access. - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2026-27172. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 1.2%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk 0.00%0.58%1.15%1.73%0.2%1.2%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## How urgent is this, really ## Where this sits among everything scored ## Real-World Exposure 2 pkgs affected ☕`org.apache.camel:camel-consul`☕`org.apache.camel:camel-consul` Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems. ## Description The ConsulRegistry in the camel-consul component (class org.apache.camel.component.consul.ConsulRegistry and its inner ConsulRegistryUtils.deserialize method) read Java-serialized values from the Consul KV store and passed them to ObjectInputStream.readObject() without configuring an ObjectInputFilter. An attacker who can write to the Consul KV store backing a Camel ConsulRegistry instance could inject a malicious serialized Java object that is deserialized the next time Camel performs a lookup against that registry, leading to arbitrary code execution in the Camel process. The issue mirrors the class of vulnerability already addressed for other Camel components in CVE-2024-22369, CVE-2024-23114 and CVE-2026-25747, and was overlooked during the original remediation of those CVEs. This issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.1. Users are recommended to upgrade to version 4.19.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.6. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.1. ## Affected Packages 2 total 2 fixed Ecosystem Package Vulnerable range Fix ☕Maven `org.apache.camel:camel-consul` ≥ 3.0.0&&< 4.14.6 4.14.6`org.apache.camel:camel-consul:4.14.6` ☕Maven `org.apache.camel:camel-consul` ≥ 4.15.0&&< 4.18.1 4.18.1`org.apache.camel:camel-consul:4.18.1` ## Affected Products 1 product · 2 configurations Application `camel`apache ≥ 4.15.0 && < 4.18.1 range ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.camel:camel-consul, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update org.apache.camel:camel-consul to 4.14.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27172 is resolved across your whole dependency graph. 3. ### Workarounds Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade. ## Frequently Asked Questions The ConsulRegistry in the camel-consul component (class org.apache.camel.component.consul.ConsulRegistry and its inner ConsulRegistryUtils.deserialize method) read Java-serialized values from the Consul KV store and passed them to ObjectInputStream.readObject() without configuring an ObjectInputFilter. An attacker who can write to the Consul KV store backing a Camel ConsulRegistry instance could inject a malicious serialized Java object that is deserialized the next time Camel performs a lookup against that registry, leading to arbitrary code execution in the Camel process. The issue mirrors t O3 Security · Impact-Aware SCA ### Is CVE-2026-27172 in your dependencies? Find it across Maven, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)