OliveTin's unsafe parsing of UniqueTrackingId can be used to write files

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L

EPSS

• CVE-2026-31817: 0.74% estimated exploitation activity in the next 30 days; percentile 54.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 —…

Published by the source

11 Mar 2026, 00:09 UTC

Last modified by the source

11 Mar 2026, 05:46 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-364q-w7vh-vhpc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-31817

Advisory: OliveTin's unsafe parsing of UniqueTrackingId can be used to write files
IDs: CVE-2026-31817, GHSA-364q-w7vh-vhpc
Record: https://patchnext.com/advisories/cve-2026-31817 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/OliveTin/OliveTin 0.0.0-20260309102040-b03af0e2eca3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/OliveTin/OliveTin: affected < 0.0.0-20260309102040-b03af0e2eca3; fixed in 0.0.0-20260309102040-b03af0e2eca3

## Suggested inspection (read-only)
- Go github.com/OliveTin/OliveTin: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/OliveTin/OliveTin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-364q-w7vh-vhpc (GitHub-reviewed advisory GHSA-364q-w7vh-vhpc lists affected ranges: Go github.com/OliveTin/OliveTin >=0 <0.0.0-20260309102040-b03af0e2eca3)

Commands are suggestions: review each one before running it.