Path Traversal in OliveTin (CVE-2026-31817)
Summary
Path traversal in OliveTin (CVE-2026-31817). Data can be tampered with by attackers. Mitigation: upgrade to 3000.11.2 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-31817 has been found in OliveTin.
Data can be tampered with by attackers.
What to do: upgrade OliveTin to 3000.11.2 or later.
If unsure, ask your IT team or search "OliveTin CVE-2026-31817" on the vendor's site.
CVE-2026-31817 (OliveTin) — CWE-22
Attack vector: remote (network-reachable) / no user interaction
Patched: 3000.11.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in OliveTin.
Check the vendor advisory for the affected versions of OliveTin.
Severity: ?. Data can be tampered with by attackers.
Update to 3000.11.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'OliveTin' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'OliveTin' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
OliveTinを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade OliveTin to 3000.11.2ステージング環境で 3000.11.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov