CVSS 3.1
7.4 highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NHigh (7.4) in apache software foundation apache camel. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExplain CVE-2026-79984 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-79984?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-79984?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-79984 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Camel | from 4.18.0 before 4.18.5 |
| Apache Software Foundation Apache Camel | from 4.19.0 before 4.22.1 |
Red Hat rates this Important.
This vulnerability is rated as Important rather than Moderate because an untrusted remote SFTP service or an adversary capable of tampering with directory listings can manipulate file paths to escape the designated polling scope, potentially exposing or altering sensitive files accessible to the client credentials. In Red Hat integration environments, the flaw specifically affects routes configured with the Camel Mina SFTP consumer to poll external file stores. Exploitation complexity is elevated because it requires either a compromised or adversarial remote host, or an active man-in-the-middle position on the network connection.
--- 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)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat build of Apache Camel 4 for Quarkus 3 | camel-mina-sftp | Affected | |
| Red Hat build of Apache Camel for Spring Boot 4 | camel-mina-sftp | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-79984.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.