CVE-2026-27172: CWE-502 Deserialization of Untrusted Data in Apache Software Foundation Apache Camel
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.
AI Analysis
Technical Summary
The vulnerability exists in the ConsulRegistry class of the camel-consul component in Apache Camel. It deserializes Java objects read from the Consul KV store without applying an ObjectInputFilter, which is necessary to prevent unsafe deserialization. An attacker able to write to the Consul KV store can inject malicious serialized Java objects. When Camel performs a lookup against the registry, these objects are deserialized, potentially leading to arbitrary code execution in the Camel process. This issue is similar to previously addressed vulnerabilities (CVE-2024-22369, CVE-2024-23114, CVE-2026-25747) but was overlooked during their remediation. The vulnerability affects Apache Camel versions from 3.0.0 up to but not including 4.14.6, and from 4.15.0 up to but not including 4.18.1. Users are advised to upgrade to 4.14.6, 4.18.1, or 4.19.0 where the issue is fixed.
Potential Impact
Successful exploitation allows an attacker with write access to the Consul KV store to execute arbitrary code within the Apache Camel process. This can compromise the integrity and availability of the affected system. The CVSS v3.1 score is 8.8 (High), reflecting network attack vector, low complexity, low privileges required, no user interaction, and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
A fix is available. Users should upgrade to Apache Camel version 4.14.6 if using the 4.14.x LTS stream, to 4.18.1 if using the 4.18.x stream, or to 4.19.0 for newer versions. These versions include the necessary patch to prevent unsafe deserialization in the ConsulRegistry component. No alternative mitigations are specified in the vendor advisory; upgrading is the recommended remediation.
CVE-2026-27172: CWE-502 Deserialization of Untrusted Data in Apache Software Foundation Apache Camel
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.
CVSS v3.1
Score 8.8high
Affected software
pkg:maven/org.apache.camel/camel-coreRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability exists in the ConsulRegistry class of the camel-consul component in Apache Camel. It deserializes Java objects read from the Consul KV store without applying an ObjectInputFilter, which is necessary to prevent unsafe deserialization. An attacker able to write to the Consul KV store can inject malicious serialized Java objects. When Camel performs a lookup against the registry, these objects are deserialized, potentially leading to arbitrary code execution in the Camel process. This issue is similar to previously addressed vulnerabilities (CVE-2024-22369, CVE-2024-23114, CVE-2026-25747) but was overlooked during their remediation. The vulnerability affects Apache Camel versions from 3.0.0 up to but not including 4.14.6, and from 4.15.0 up to but not including 4.18.1. Users are advised to upgrade to 4.14.6, 4.18.1, or 4.19.0 where the issue is fixed.
Potential Impact
Successful exploitation allows an attacker with write access to the Consul KV store to execute arbitrary code within the Apache Camel process. This can compromise the integrity and availability of the affected system. The CVSS v3.1 score is 8.8 (High), reflecting network attack vector, low complexity, low privileges required, no user interaction, and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
A fix is available. Users should upgrade to Apache Camel version 4.14.6 if using the 4.14.x LTS stream, to 4.18.1 if using the 4.18.x stream, or to 4.19.0 for newer versions. These versions include the necessary patch to prevent unsafe deserialization in the ConsulRegistry component. No alternative mitigations are specified in the vendor advisory; upgrading is the recommended remediation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-02-18T14:18:10.063Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-27172","vendor":"Red Hat"}]
Threat ID: 69ef3e3cba26a39fba196b2b
Added to database: 04/27/2026, 10:45:16 UTC
Last enriched: 07/15/2026, 08:43:37 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 165
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.