CVE-2026-31817: OliveTin's unsafe parsing of UniqueTrackingId can be used to write files
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.
References
- github.com/OliveTin/OliveTin
- github.com/OliveTin/OliveTin/commit/2f77000de44f65690f257e3cf8e2c8462b0e74c7
- github.com/OliveTin/OliveTin/releases/tag/3000.11.2
- github.com/OliveTin/OliveTin/security/advisories/GHSA-364q-w7vh-vhpc
- github.com/advisories/GHSA-364q-w7vh-vhpc
- nvd.nist.gov/vuln/detail/CVE-2026-31817
Code Behaviors & Features
Detect and mitigate CVE-2026-31817 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →