CVE-2026-31817
Directory Traversal in OliveTin Logs Allows Arbitrary File Write
Publication date: 2026-03-10
Last updated on: 2026-03-12
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| olivetin | olivetin | to 3000.11.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in OliveTin versions prior to 3000.11.2 when the saveLogs feature is enabled. OliveTin saves execution log entries to disk using filenames that include a user-supplied UniqueTrackingId field from the StartAction API request. Because this field is not validated or sanitized, an attacker can include directory traversal sequences (such as ../../../) in the UniqueTrackingId. This allows the attacker to write files to arbitrary locations on the filesystem, potentially overwriting or creating files outside the intended directory.
How can this vulnerability impact me? :
The vulnerability can allow an attacker with limited privileges to write files to arbitrary locations on the server's filesystem. This can lead to unauthorized modification or creation of files, potentially enabling further attacks such as privilege escalation, denial of service, or persistent compromise of the system. The CVSS score indicates a high impact on integrity and a low impact on availability, with no impact on confidentiality.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade OliveTin to version 3000.11.2 or later, where the issue is fixed.
Additionally, if the saveLogs feature is enabled, consider disabling it temporarily until the upgrade can be applied to prevent exploitation via directory traversal in log file paths.