Security readout for executives and security teams
Plain-English summary
Apache Camel applications using the camel-consul registry can be compromised if an attacker can write malicious data into the backing Consul KV store. Camel may deserialize that data during a registry lookup, allowing code execution inside the Camel process. The business risk is high where Consul write access is broad or shared across teams.
Executive priority
Treat this as a high-priority remediation for Camel services using Consul-backed registries. The issue can lead to full process compromise, but exploitation depends on Consul KV write access. Patch exposed services and tighten KV permissions promptly.
Technical view
ConsulRegistry in org.apache.camel:camel-consul deserializes Java-serialized KV values with ObjectInputStream.readObject() without an ObjectInputFilter. This is CWE-502 unsafe deserialization. Affected versions are Apache Camel 3.0.0 before 4.14.6 and 4.15.0 before 4.18.1. Apache recommends upgrading to 4.19.0, or 4.14.6/4.18.1 for those streams.
Likely exposure
Exposure is likely limited to Apache Camel deployments that use camel-consul ConsulRegistry backed by Consul KV. Risk rises when non-administrative users, services, CI jobs, or tenants can write to that KV path. Deployments not using camel-consul or ConsulRegistry are not indicated as affected by the provided sources.
Exploitation context
The attacker needs permission to write to the Consul KV store backing the Camel registry. The malicious object is processed when Camel performs a lookup against that registry. The bundle states KEV is false and provides no source evidence of active exploitation.
Researcher notes
This mirrors prior Camel deserialization fixes and was missed for camel-consul. The vulnerable flow is ConsulRegistryUtils.deserialize reading Java-serialized KV data without an ObjectInputFilter. Evidence does not establish public exploitation, exploit maturity, or affected downstream product status beyond the listed references.
Mitigation direction
- Upgrade Apache Camel to 4.19.0 where possible.
- On 4.14.x LTS, upgrade to 4.14.6.
- On the 4.18.x stream, upgrade to 4.18.1.
- Restrict Consul KV write access to trusted service identities.
- Review vendor and distribution advisories for downstream package status.
Validation and detection
- Inventory applications using org.apache.camel:camel-consul.
- Check deployed Camel versions against the affected ranges.
- Confirm whether ConsulRegistry is configured in each application.
- Review Consul ACLs for write access to registry KV paths.
- Prioritize systems where untrusted or shared identities can write KV data.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-27172 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9CISA-ADPCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-04-27T11:01:05.510Z: Reported to Red Hat.
- 2026-04-27T09:59:45.503Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://camel.apache.org/security/CVE-2026-27172.htmlCVE reference, apache · vendor-advisory
- https://access.redhat.com/security/cve/CVE-2026-27172CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2463183CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-27172.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.