Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:LSummary
CVE-2026-31817 is a high-severity Path Traversal (CWE-22) vulnerability in Olivetin Olivetin. Its CVSS base score is 8.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 50% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-31817 is a path traversal vulnerability (CWE-22) affecting OliveTin, an open-source web interface for executing predefined shell commands, in versions prior to 3000.11.2. When the saveLogs feature is enabled, OliveTin writes execution log entries to disk using a filename partially constructed from the user-supplied UniqueTrackingId field in the StartAction API request. This field lacks validation or sanitization, enabling attackers to inject directory traversal sequences such as "../../../" to direct log files to arbitrary filesystem locations.
The vulnerability has a CVSS v3.1 base score of 8.5 (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L), indicating exploitation over the network with low complexity by low-privileged authenticated users and no user interaction required. Successful exploitation allows attackers to write files to arbitrary paths on the server filesystem, potentially enabling persistence, configuration overwrites, or further compromise depending on write permissions and locations targeted, with high integrity impact, changed scope, low availability impact, and no confidentiality impact.
The OliveTin security advisory at https://github.com/OliveTin/OliveTin/security/advisories/GHSA-364q-w7vh-vhpc confirms the issue and states it is fixed in version 3000.11.2 by addressing the lack of sanitization in the UniqueTrackingId handling. Security practitioners should upgrade to 3000.11.2 or later and disable saveLogs if not needed, while reviewing access controls on the StartAction API endpoint.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-10910
Vulnerability Data
OliveTin gives access to predefined shell commands from a web interface. Prior to 3000.11.2, when the saveLogs feature is enabled, OliveTin persists execution log entries to disk. The filename used for these log files is constructed in part from the…
more
user-supplied UniqueTrackingId field in the StartAction API request. This value is not validated or sanitized before being used in a file path, allowing an attacker to use directory traversal sequences (e.g., ../../../) to write files to arbitrary locations on the filesystem. This vulnerability is fixed in 3000.11.2.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
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.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
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.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.