Code execution via unfiltered Consul value deserialization
Published Apr 27, 2026 · Updated Apr 27, 2026
Unsafe deserialization in Apache Camel 3.0.0 through 4.14.5 and 4.15.0 through 4.18.0 allows attackers to execute code via Consul KV data. ConsulRegistryUtils.deserialize passes Base64-decoded store values to ObjectInputStream.readObject without an ObjectInputFilter or class allowlist. Exploitation requires write access to the registry's Consul KV store and a subsequent Camel registry lookup, after which code runs in the Camel process.
Summary
What happened
Unsafe deserialization in Apache Camel 3.0.0 through 4.14.5 and 4.15.0 through 4.18.0 allows attackers to execute code via Consul KV data. ConsulRegistryUtils.deserialize passes Base64-decoded store values to ObjectInputStream.readObject without an ObjectInputFilter or class allowlist. Exploitation requires write access to the registry's Consul KV store and a subsequent Camel registry lookup, after which code runs in the Camel process.
The record
- CVE
- CVE-2026-27172
- Published
- Apr 27, 2026
- Updated
- Apr 27, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Camel
- Classifications
- CWE-502
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 27, 2026CVE publishedPublication date reported by the CVE source.
- Apr 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.0 <4.14.6
- Affected versionversion=4.15.0 <4.18.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo