High8.8Apache Software Foundation

High [CVE-2024-22369 +3] Apache Camel: Unsafe Java deserialization in camel-consul ConsulRegistry allows arbitrary code execution via malicious values read from the Consul KV store

This high-severity Apache Software Foundation advisory covers CVE-2024-22369 and CVE-2024-23114 and 2 more CVEs affecting Apache Camel.

CVE-2026-27172 Published Apr 27, 2026Updated by vendor Jul 15, 2026

CVE-2024-22369 CVE-2024-23114 CVE-2026-25747 CVE-2026-27172

Affected products & platforms

Apache Software FoundationMessaging

Open vendor advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Get CVE alerts See app features

Summary

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.

Affected versions

Apache Camel 3.0.0 before 4.14.6
Apache Camel 4.15.0 before 4.18.1

Official advisory · high-confidence parse· fetched 1 month ago·verify at source

Fixed versions

4.14.6
4.18.1

Official advisory · high-confidence parse· fetched 1 month ago·verify at source

Mitigation checklist

Recommended fix / mitigation

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.

Official advisory · high-confidence parse· fetched 1 month ago·verify at source

Sources

Official and corroborating records used to build this advisory.

CVE.org CNA affected-product recordCVE.org
Structured CNA affected[] data independently confirmed the affected product scope; native advisory content remains authoritative.
CVE Program
CVE.org CNA affected-product recordCVE.org
Structured CNA affected[] data independently confirmed the affected product scope; native advisory content remains authoritative.
CVE Program
NVD discovery recordNVD
Independent discovery and scoring cross-reference. Vendor remediation guidance takes precedence. Discovered from the machine-readable feed https://services.nvd.nist.gov/rest/json/cves/2.0; this link opens the NVD record for CVE-2024-22369 instead of the raw feed document.
NIST National Vulnerability Database

Cross-references

Validate CVE metadata against the authoritative registries.

Official resources

ASF Security — reporting & CVE process
Official documentation
The Apache Software Foundation's official security page: how ASF CVEs are published and where each project's advisories live.
Apache project downloads (fixed releases)
Official documentation
Official ASF download tree — fetch the fixed release named in this advisory from the project's directory.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.