CVE-2026-31817 is a high-severity path traversal vulnerability in github.com/OliveTin/OliveTin (go), affecting versions < 0.0.0-20260309102040-b03af0e2eca3. It is fixed in 0.0.0-20260309102040-b03af0e2eca3.
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 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. Affected Code Entry point, service/internal/api/api.go (line 130): The UniqueTrackingId from the API request is passed directly to the executor without validation: Tracking ID accepted as-is, service/internal/executor/executor.go (lines 508–512): The tracking ID is only replaced with a UUID if it is empty or a duplicate. Any other string, including one containing path separators, is accepted: Filename construction, service/internal/executor/executor.go (line 1042): The tracking ID is interpolated directly into the log filename: File write, service/internal/executor/executor.go (lines 1068–1069 and 1082–1083): The filename is joined to the configured log directory using path.Join, which calls path.Clean internally. path.Clean resolves .. path segments, causing the final file path to escape the intended directory: Proof of Concept An attacker sends the following StartAction request (Connect RPC or REST): Assuming the action title is Ping the Internet and the timestamp is 1741320000, the constructed filename becomes: When path.Join processes this with a configured results directory like /var/olivetin/logs: path.Clean resolves the traversal: Path segments: ["var", "olivetin", "logs", "Ping the Internet.1741320000...", "..", "..", "..", "tmp", "pwned.yaml"] The .. segments traverse upward past the log directory. Final resolved path: /tmp/pwned.yaml Two files are written: .yaml file, contains YAML-serialized InternalLogEntry (action title, icon, timestamps, exit code, output, tags, username, tracking ID) .log file, contains the raw command output (potentially attacker-influenced if the action echoes its arguments) Impact Arbitrary file write to any path writable by the OliveTin process. OliveTin frequently runs as root inside Docker containers, so the writable scope is often the entire filesystem. An attacker could: Overwrite OliveTin's own sessions.yaml to inject authenticated sessions. Write to entity file directories to inject malicious entity data. Write to system cron directories or other locations to achieve remote code execution. Cause denial of service by overwriting critical system files. Suggested Fix Validate the UniqueTrackingId to ensure it only contains safe characters before use. A strict UUID format check is the simplest approach: Alternatively, sanitize the filename in stepSaveLog by stripping or rejecting path separators and .. sequences.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
CVE-2026-31817 has a CVSS score of 8.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (0.0.0-20260309102040-b03af0e2eca3). Upgrading removes the vulnerable code path.
go
github.com/OliveTin/OliveTin (< 0.0.0-20260309102040-b03af0e2eca3)github.com/OliveTin/OliveTin → 0.0.0-20260309102040-b03af0e2eca3 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-31817 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-31817 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-31817 in your environment →Upgrade github.com/OliveTin/OliveTin to 0.0.0-20260309102040-b03af0e2eca3 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-31817 is a high-severity path traversal vulnerability in github.com/OliveTin/OliveTin (go), affecting versions < 0.0.0-20260309102040-b03af0e2eca3. It is fixed in 0.0.0-20260309102040-b03af0e2eca3. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
CVE-2026-31817 has a CVSS score of 8.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
github.com/OliveTin/OliveTin (go) versions < 0.0.0-20260309102040-b03af0e2eca3 is affected.
Yes. CVE-2026-31817 is fixed in 0.0.0-20260309102040-b03af0e2eca3. Upgrade to this version or later.
Whether CVE-2026-31817 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade github.com/OliveTin/OliveTin to 0.0.0-20260309102040-b03af0e2eca3 or later.