Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Unsafe Java deserialization in Apache Camel camel-consul ConsulRegistry

IdentifiersCVE-2026-27172CWE-502· Deserialization of Untrusted Data

CVE-2026-27172 is an unsafe deserialization vulnerability in the camel-consul component of Apache Camel. The flaw is in org.apache.camel.component.consul.ConsulRegistry, including its inner ConsulRegistryUtils.deserialize method, which reads Java-serialized values from the Consul KV store and passes them to ObjectInputStream.readObject() without configuring an ObjectInputFilter or equivalent class restrictions. Because the deserialization input is sourced from the backing Consul KV store, an attacker who can write a malicious serialized Java object into that store can cause Camel to deserialize attacker-controlled data during a subsequent registry lookup. The affected execution path includes ConsulRegistry lookup operations, and successful exploitation can result in arbitrary code execution within the Camel process. Apache states the issue affects versions 3.0.0 before 4.14.6 and 4.15.0 before 4.18.1, and that it was an overlooked instance of the same vulnerability class previously addressed in other Camel components.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary code execution in the context of the Apache Camel process. In practice, this can let an attacker execute code via a deserialization gadget chain when Camel performs a lookup against the affected ConsulRegistry backed by attacker-controlled KV data. The resulting impact depends on the privileges of the Camel runtime and may include full compromise of the integration service, access to application data and secrets available to the process, further lateral movement from the host, and persistence or service disruption.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, strictly restrict and monitor write access to the Consul KV store used by Camel ConsulRegistry instances, prevent untrusted parties or services from inserting serialized values into that store, and avoid using the vulnerable ConsulRegistry functionality for untrusted data. Additional compensating controls include reducing network and administrative access to Consul, auditing KV writes, and limiting the privileges of the Camel process to reduce post-exploitation impact.

Remediation

Patch, then assume compromise.

Upgrade to a fixed Apache Camel release. Apache recommends upgrading to 4.19.0. For users remaining on supported release streams, upgrade 4.14.x to 4.14.6 or 4.18.x to 4.18.1. These releases address the unsafe deserialization behavior in camel-consul ConsulRegistry.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationCamelapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.