Red Hat Security Advisory: Red Hat Build of Apache Camel 4.22 for Quarkus 3.40 update is now available (RHBQ 3.40.1.GA)
🔗 CVE IDs covered (9)
📋 Description
CVE-2026-59230 — org.apache.camel/camel-mail: Apache Camel: Injected MIME headers can manipulate route behavior CVE-2026-78164 — org.apache.camel/camel-http-common: org.apache.camel/camel-http: org.apache.camel/camel-vertx-http: org.apache.camel/camel-undertow: org.apache.camel/camel-netty-http: Apache Camel: information disclosure via improper property placeholder evaluation in HTTP headers CVE-2026-79983 — org.apache.camel/camel-ftp: camel-ftp: Unauthorized remote file access via path traversal CVE-2026-79984 — org.apache.camel/camel-mina-sftp: Apache Camel Mina SFTP: Unauthorized file access via path traversal CVE-2026-79985 — org.apache.camel/camel-smb: camel-smb: Unauthorized file access via path traversal CVE-2026-80343 — org.apache.camel/camel-netty-http: Apache Camel Netty HTTP: Security constraint bypass via case sensitivity mismatch CVE-2026-85250 — org.apache.camel/camel-xpath: camel-xpath: Information disclosure via XML external entity references CVE-2026-85251 — org.apache.camel/camel-http: camel-http: Information disclosure via improper credential handling during HTTP redirects CVE-2026-88901 — org.apache.camel/camel-smooks: camel-smooks: Information disclosure via XML external entity injection
🎯 Affected products200
- Red Hat Build of Apache Camel 3.40.1.redhat
- ai.docling.docling-core-0.5.0.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ai.docling.docling-serve-api-0.5.0.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ai.docling.docling-serve-client-0.5.0.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- aopalliance.aopalliance-1.0.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- at.yawk.lz4.lz4-java-1.11.4.rhel8-redhat-00001.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- biz.aQute.bnd.biz.aQute.bnd.transform-6.3.1.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.hapi-fhir-base-8.10.0.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.hapi-fhir-caching-api-8.10.0.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.hapi-fhir-client-8.10.0.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.hapi-fhir-structures-dstu2-8.10.1.redhat-00001.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.hapi-fhir-structures-dstu2.1-8.10.0.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.hapi-fhir-structures-dstu3-8.10.0.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.hapi-fhir-structures-hl7org-dstu2-8.10.0.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.hapi-fhir-structures-r4-8.10.0.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.hapi-fhir-structures-r5-8.10.0.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.org.hl7.fhir.dstu2-6.9.12.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.org.hl7.fhir.dstu2016may-6.9.12.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.org.hl7.fhir.dstu3-6.9.12.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.org.hl7.fhir.r4-6.9.12.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.org.hl7.fhir.r5-6.9.12.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.fhir.org.hl7.fhir.utilities-6.9.12.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- ca.uhn.hapi.hapi-base-2.6.0.redhat-00002.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- co.elastic.clients.elasticsearch-rest5-client-9.4.1.redhat-00001.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- com.aayushatharva.brotli4j.brotli4j-1.24.0.redhat-00001.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- com.aayushatharva.brotli4j.native-linux-x86_64-1.24.0.redhat-00001.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- com.aayushatharva.brotli4j.service-1.24.0.redhat-00001.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- com.amazonaws.dynamodb-lock-client-1.4.0.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- com.atlassian.event.atlassian-event-6.0.0.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- com.atlassian.httpclient.atlassian-httpclient-api-4.0.1.jar as a component of Red Hat Build of Apache Camel 3.40.1.redhat
- +170 more not shown
✅ Remediation
Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings, and so on. The References section of this erratum contains a download link (you must log in to download the update). Workaround: Users should upgrade to Apache Camel 4.14.9, 4.18.4, or 4.22.0, as applicable to their release stream. Where an upgrade is not immediately possible, keep headersInline=false unless inline MIME headers are required. If headersInline=true must remain enabled, remove Camel-internal headers immediately after the unmarshalling step, before any processor or producer reads Camel control headers. For example, routes may use removeHeaders("Camel*") as a defense-in-depth measure. Do not unmarshal MIME content from an untrusted sender into a route that dispatches or performs sensitive operations based on message header values. Treat MIME header names received from outside the trust boundary as untrusted input. Workaround: --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to eliminate property placeholder resolution on message-supplied URI override headers in Apache Camel HTTP producer components: upgrade to Apache Camel 4.18.5, 4.22.1, or 4.23.0 (or the fixed Camel Http Common/Camel Http/Camel Vertx Http/Camel Undertow/Camel Netty Http builds), which remove property placeholder resolution on message-supplied URI override headers across HTTP producer helper methods, closing all 3 injection vectors (property placeholder injection via CamelHttpUri header, property placeholder injection via CamelRestHttpUri header, request-line placeholder injection via reverse-proxy consumers). Until patched, this is a concern on deployments using Apache Camel HTTP producer components handling untrusted message exchanges, so strip CamelHttpUri and CamelRestHttpUri headers at trust boundaries prior to routing to HTTP producers, or configure skipControlHeaders=true on camel-http endpoints. As a compensating measure, apply allowlist validation to inbound headers or strip unexpected control headers such as CamelHttpUri before message exchanges reach HTTP producers. These controls limit blast radius and contain exploitation, but they do not fix the underlying improper property placeholder evaluation defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1309 Script Engine Restriction (Sandbox / Disable) (high) Workaround: --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce path normalization and boundary containment checks on remote directory listing entries before dispatching remote file operations in Camel remote-file consumers: upgrade to Apache Camel 4.18.5, 4.22.1, or 4.23.0 (or the fixed Camel Ftp builds), which validate that normalized remote file paths remain within the starting directory and skip out-of-bounds files during directory listing consumption, closing all 2 injection vectors (malicious remote server directory listing entries, on-path tampering with unencrypted FTP LIST responses). Until patched, this is a concern on Camel routes configured to consume remote files via ftp, ftps, or sftp endpoints, so use encrypted protocols such as FTPS or SFTP with verified host keys, avoid destructive consumer options like delete or move, jail server-side accounts, and apply filters restricting filenames to single path segments. As a compensating measure, Enforce application-level scoping to confine file operations strictly to the configured base polling directory and Canonicalize received directory listing filenames before evaluating containment and dispatching remote file operations. These controls limit blast radius and contain exploitation, but they do not fix the underlying path traversal defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1301 Path Traversal Prevention (Canonicalization) (high) Workaround: --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce separator-aware containment checks and lexical normalization on remote directory listing entries before invoking file retrieval, deletion, or renaming operations: upgrade to Apache Camel 4.18.5, 4.22.1, or 4.23.0+ (or the fixed Camel Mina Sftp builds), which skip listing entries that resolve outside the configured starting directory using separator-aware containment checks, closing all 3 injection vectors (crafted remote directory listing entries, on-path directory listing response manipulation, crafted fileName expressions with traversal segments). Until patched, this is a concern on Camel applications with remote-file consumers polling untrusted, multi-tenant, or network-exposed servers, so Constrain consumer filenames to single segments via filter or include patterns, avoid destructive disposition options such as delete or move, verify remote host keys, and confine remote accounts on the server. As a compensating measure, Restrict path characters by rejecting directory listing entries containing non-allowlisted characters or traversal sequences prior to path concatenation and Encrypt transport traffic using IPsec or WireGuard to prevent on-path network adversaries from tampering with directory listing responses. These controls limit blast radius and contain exploitation, but they do not fix the underlying path traversal defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1301 Path Traversal Prevention (Canonicalization) (high) Workaround: --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce directory containment and boundary validation on remote directory listing paths within Camel remote-file consumers before invoking file retrieval or management operations: upgrade to Apache Camel 4.18.5, 4.22.1, or 4.23.0 (or the fixed Camel Smb builds), which compact and verify that resolved remote paths remain within the starting directory, skipping non-conforming entries with a warning, closing all 3 injection vectors (crafted directory listing entries containing path traversal sequences, on-path modification of unencrypted directory listing responses, malicious or compromised remote file server responses). Until patched, this is a concern on Camel routes configured to poll remote files using remote-file consumer components, so restrict consumer connections to trusted remote servers, restrict file consumer include filters to single path segments, and disable destructive options such as delete or move on untrusted endpoints. As a compensating measure, canonicalize directory listing path segments before containment chec…
🔗 References (21)
- selfhttps://access.redhat.com/errata/RHSA-2026:98783
- externalhttps://access.redhat.com/security/updates/classification/#important
- externalhttps://access.redhat.com/security/cve/CVE-2026-80343
- externalhttps://access.redhat.com/security/cve/CVE-2026-85251
- externalhttps://access.redhat.com/security/cve/CVE-2026-79983
- externalhttps://access.redhat.com/security/cve/CVE-2026-79984
- externalhttps://access.redhat.com/security/cve/CVE-2026-78164
- externalhttps://access.redhat.com/security/cve/CVE-2026-79985
- externalhttps://access.redhat.com/security/cve/CVE-2026-85250
- externalhttps://access.redhat.com/security/cve/CVE-2026-88901
- externalhttps://access.redhat.com/security/cve/CVE-2026-59230
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2522054
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2555477
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2555481
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2555482
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2555484
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2555495
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2555504
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2555511
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2555518
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_98783.json