dbcve.org
CamelApplication · Apache

CVE-2026-27172

HIGH · 8.8 CVSS v3.1 Published 2026-04-27
Fix available
A fix is available. Upgrade to 4.14.6 / 4.18.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The ConsulRegistry in Apache Camel's camel-consul component reads Java-serialized values from the Consul KV store and deserializes them via ObjectInputStream.readObject() without an ObjectInputFilter. An attacker with write access to the Consul KV store can inject malicious serialized objects that execute arbitrary code upon Camel registry lookup.

MitigationUpgrade Apache Camel to version 4.19.0, 4.14.6 (LTS), or 4.18.1. If upgrade is not immediately possible, restrict write access to the Consul KV store to trusted parties only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CamelApplication
Affected:>= 3.0.0, < 4.14.6>= 4.15.0, < 4.18.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Camel version
    Locate the camel-core JAR file or check your build file (pom.xml, gradle.build) for the Apache Camel version. Run 'mvn dependency:tree | grep camel-core' or inspect the classpath for 'camel-core-*.jar'.
    Affected if The version is >= 3.0.0 and < 4.14.6, or >= 4.15.0 and < 4.18.1
  2. Confirm camel-consul component is present
    Check your build dependencies for 'camel-consul' or search your codebase for imports of 'org.apache.camel.component.consul' packages. Inspect your classpath for 'camel-consul-*.jar'.
    Affected if The camel-consul component is on the classpath or referenced in your Camel routes or configuration.
  3. Verify ConsulRegistry is in use
    Search your Java/XML configuration files for 'ConsulRegistry' bean definitions or look for 'registry:consul' in your Camel route definitions. Check application context files for ConsulRegistry instantiation.
    Affected if ConsulRegistry is configured as the Camel registry, enabling the KV store deserialization path.

You are affected if your Apache Camel version falls within the vulnerable range AND you are using the camel-consul component with ConsulRegistry enabled, allowing deserialization of objects from the Consul KV store.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.14.6 / 4.18.1 or later
Fixed in 4.14.64.18.1
Interim mitigation

Upgrade Apache Camel to version 4.19.0, 4.14.6 (LTS), or 4.18.1. If upgrade is not immediately possible, restrict write access to the Consul KV store to trusted parties only.

Recommended fix High confidence

4.14.6 (for 4.14.x LTS), 4.18.1 (for 4.18.x), or 4.19.0+ (for other affected versions)

  1. 1. Identify the current Apache Camel version in use by checking project dependencies or the camel-core JAR manifest
  2. 2. Determine which release stream is in use: 3.x, 4.14.x LTS, or 4.18.x
  3. 3. For 4.14.x LTS stream: upgrade to version 4.14.6
  4. 4. For 4.18.x stream: upgrade to version 4.18.1
  5. 5. For all other affected versions: upgrade to version 4.19.0 or later
  6. 6. Update the Maven pom.xml or build configuration to use the new Camel version
  7. 7. Rebuild and redeploy the application
  8. 8. Verify that the camel-consul component loads correctly and lookups function as expected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Camel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27172 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27172 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data