Is this vulnerability remotely exploitable?

Yes, in typical deployments it can be triggered remotely through the web-exposed StartAction API, as long as the attacker can submit requests containing a crafted UniqueTrackingId while saveLogs is enabled.

What level of access does an attacker need?

The attacker must be able to invoke the StartAction API and control the UniqueTrackingId field. Whether that requires authentication depends on how OliveTin is configured, but the issue does not require shell access or local filesystem access on the host.

What is the safest general fix pattern?

The most robust fix is to treat UniqueTrackingId purely as a logical identifier, restrict it to a safe character set and length, and resolve all log file paths exclusively within a predefined log directory using canonicalization to prevent directory traversal. File path construction should not trust any client-controlled data.

Severity:

HIGH RISK

(8.5)

Path Traversal File Write (CWE-22) in OliveTin saveLogs Feature

CVE-2026-31817

Published:

Mar 10, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Path Traversal / Directory Traversal

CWE:

CWE-22

Impact:

Arbitrary File Write on Server Filesystem

Severity:

HIGH RISK

(8.5)

CVSS Version:

3.1

Vulnerability Type

Category:

Path Traversal / Directory Traversal

CWE:

CWE-22

Impact:

Arbitrary File Write on Server Filesystem

Severity:

HIGH RISK

(8.5)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Path Traversal File Write (CWE-22) in OliveTin saveLogs Feature

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal