CVE-2026-104706
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:X/RE:X/U:AmberCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-104706 is a high-severity Path Traversal: 'dir\..\..\filename' (CWE-31) vulnerability in Digitalcanion (inferred from references). Its CVSS base score is 8.4 (High).
Operationally, ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-92289
Vulnerability Data
DigitalCanion has discovered a path traversal vulnerability that allows to view or download sensitive system files over the portal https://<ip>:8443 via menus Administration -> View Logs
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Enforces authorization checks on file/resource access, blocking exploitation of a traversed path even if the malformed name is accepted.
Enforces information flow rules that can deny access to locations outside the intended directory.
Directly requires validation of path inputs, stopping the acceptance of backslash dot-dot sequences that escape the restricted directory.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and path sanitization that block this weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure development lifecycle mandates input validation and path sanitization that directly blocks directory traversal sequences.
A.8.26 only requires that security requirements (including resilience against SQLi or buffer overflows) be identified and specified during development or acquisition; it does not itself neutralize path traversal sequences or stop exploitation of CWE-31.
Secure architecture principles reduce the attack surface but do not prescribe the specific coding fix.
Secure coding standards require canonicalization and whitelist validation that eliminate CWE-31.