# CVE-2026-31817: OliveTin's unsafe parsing of UniqueTrackingId can be used to write files > Attackers can write arbitrary files via directory traversal in log filenames when saveLogs is enabled, requiring an upgrade to fix. - **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Mar 2026 - **Updated:** 11 Mar 2026 - **Also known as:** GHSA-364q-w7vh-vhpc, GO-2026-4670 ## What is CVE-2026-31817? CVE-2026-31817 is a high-severity path traversal vulnerability in OliveTin, published on 10 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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 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. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-31817? 3 open source packages ship an affected version, including github.com/OliveTin/OliveTin. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/OliveTin/OliveTin` | Go | All versions | 0.0.0-20260309102040-b03af0e2eca3 | | `github.com/OliveTin/OliveTin` | Go | All versions | 0.0.0-20260309102040-b03af0e2eca3 | | `github.com/OliveTin/OliveTin` | Go | All versions | 0.0.0-20260309102040-b03af0e2eca3 | Products: Olivetin Olivetin. ## How do I fix CVE-2026-31817? Upgrade github.com/OliveTin/OliveTin to 0.0.0-20260309102040-b03af0e2eca3 or later. ## Is CVE-2026-31817 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31817 exists. ## Other vulnerabilities in OliveTin - [CVE-2026-27626](https://insights.sbomify.com/CVE-2026-27626/): OliveTin: OS Command Injection via `password` argument type and webhook JSON extraction bypasses shell safety checks (critical 10.0) - [CVE-2026-30223](https://insights.sbomify.com/CVE-2026-30223/): OliveTin: JWT Audience Validation Bypass in Local Key and HMAC Modes (high 8.8) - [CVE-2026-28342](https://insights.sbomify.com/CVE-2026-28342/): OliveTin: Unauthenticated Denial of Service via Memory Exhaustion in PasswordHash API Endpoint (high 7.5) - [CVE-2026-28789](https://insights.sbomify.com/CVE-2026-28789/): OliveTin: Unauthenticated DoS via concurrent map writes in OAuth2 state handling (high 7.5) - [CVE-2026-28790](https://insights.sbomify.com/CVE-2026-28790/): OliveTin: Unauthenticated Action Termination via KillAction When Guests Must Login (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-31817 and fix it if it is affected. What it is: CVE-2026-31817 is a high-severity path traversal vulnerability in OliveTin, published on 10 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31817 exists. Affected packages and fixed versions: - github.com/OliveTin/OliveTin (Go): affected all versions; fixed in 0.0.0-20260309102040-b03af0e2eca3 - github.com/OliveTin/OliveTin (Go): affected all versions; fixed in 0.0.0-20260309102040-b03af0e2eca3 - github.com/OliveTin/OliveTin (Go): affected all versions; fixed in 0.0.0-20260309102040-b03af0e2eca3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-31817/ (Markdown: https://insights.sbomify.com/CVE-2026-31817/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-31817 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-31817 - OSV: https://osv.dev/vulnerability/CVE-2026-31817 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-31817/ Summaries are generated and may contain mistakes; the official description above is the record.