CVE-2026-79985
Description
A flaw was found in the Apache Camel Server Message Block (SMB) component, leading to information disclosure and unauthorized file tampering. When retrieving files from a remote share, the component fails to properly validate and restrict file paths returned in directory listings. A compromised or malicious remote server can supply directory entries containing path traversal sequences, causing the application to read, rename, or delete arbitrary files outside the configured directory using the connection's credentials.
Statement
This vulnerability is rated with an Important severity because untrusted directory data could allow an adversary controlling a remote file share to access, alter, or remove files outside the designated directory using the application's authenticated session. In Red Hat build of Apache Camel, exposure is confined to integration routes actively employing the optional camel-smb consumer to poll external shares. Under typical operational conditions, conforming SMB2 servers do not supply directory entries containing path traversal elements, meaning successful exploitation requires connecting to a compromised, rogue, or multi-tenant file server.
Mitigation
--- 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 checks to eliminate unnormalized traversal tokens and deploy transport-layer encryption and integrity protection such as IPsec or WireGuard to prevent on-path tampering with directory listings. 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)
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.4 | N/A | 7.4 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
