CVE-2026-27172 Apache Camel-Consul component vulnerable to Deserialization of Untrusted Data
An attacker with write access to the Consul KV store can inject malicious serialized objects to achieve arbitrary code execution in Apache Camel applications.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-27172?
CVE-2026-27172 is a high-severity unsafe deserialization vulnerability in Apache Camel, published on 27 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-502
Which versions are affected by CVE-2026-27172?
4 open source packages ship an affected version, including org.apache.camel:camel-consul. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.apache.camel:camel-consul Maven | From 3.0.0 | 4.14.6 |
org.apache.camel:camel-consul Maven | From 3.0.0 | 4.14.6 |
org.apache.camel:camel-consul Maven | From 4.15.0 | 4.18.1 |
org.apache.camel:camel-consul Maven | From 4.15.0 | 4.18.1 |
Products include Apache Camel.
How do I fix CVE-2026-27172?
Upgrade org.apache.camel:camel-consul to a fixed version for your release line: 4.14.6 or 4.18.1.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2026-27172 being exploited?
There is no known exploitation of CVE-2026-27172 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Other vulnerabilities in Apache Camel
- CVE-2026-33453 Apache camel-coap allows header injection that can lead to remote code execution
- CVE-2026-40453 Apache Camel has an incomplete fix for CVE-2025-27636
- CVE-2026-80351 Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod
- CVE-2026-80352 Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects
- CVE-2026-71300 Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection
Sources
Also known as GHSA-5rc6-9qfp-8vwg.