CVE-2026-27172: Apache Camel: Unsafe Java deserialization in camel-consul ConsulRegistry allows arbitrary code execution via malicious values read from the Consul KV store

Published Apr 26, 2026
·
Updated

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 Software

3 affected components
Apache Apache Camel>=3.0.0<4.14.6, >=4.15.0<4.18.1
Apache Camel>=3.0.0<4.14.6
Apache Camel>=4.15.0<4.18.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apache Camel (camel-consul / ConsulRegistry) to a version that resolves this vulnerability.

    Fixed in 4.14.6
  2. Upgrade

    Upgrade Apache Camel (camel-consul / ConsulRegistry) to a version that resolves this vulnerability.

    Fixed in 4.18.1
  3. Upgrade

    Upgrade Apache Camel (camel-consul / ConsulRegistry) to a version that resolves this vulnerability.

    Fixed in 4.19.0

Event History

Apr 27, 2026
CVE Published
via MITRE·09:59 AM
Data Sourced
via MITRE·09:59 AM
DescriptionWeakness
Data Sourced
via Red Hat·11:01 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·11:16 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-27172?

The severity of CVE-2026-27172 is critical due to the potential for arbitrary code execution.

2

How do I fix CVE-2026-27172?

To fix CVE-2026-27172, upgrade Apache Camel to a version above 4.14.6 or 4.18.1.

3

What software is affected by CVE-2026-27172?

CVE-2026-27172 affects Apache Camel versions between 3.0.0 to 4.14.6 and 4.15.0 to 4.18.1.

4

What vectors allow exploitation of CVE-2026-27172?

Exploitation of CVE-2026-27172 is possible through unsafe Java serialization and malicious values from the Consul KV store.

5

What are the implications of not addressing CVE-2026-27172?

Failing to address CVE-2026-27172 could lead to unauthorized remote code execution, compromising system security.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203