Daytona: Path traversal in sandbox volume id mounts arbitrary host paths into the sandbox — cross-tenant data access and host escape

published 2026-06-18 4 mo ago modified 2026-10-25 14 d ago also GHSA-fjv8-j4p5-cr9m , GO-2026-5367 , EUVD-2026-38564

cvss: 4.2; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 15%
public exploits: 0; none known

Daytona is a secure and elastic infrastructure runtime for AI-generated code execution and agent workflows. Prior to 0.186, a sandbox volume reference (volumeId, which may also be a volume name) was forwarded to the runner and used to build the host bind-mount source path without confinement. A reference containing path-traversal sequences could in principle resolve the mount source outside the intended per-volume base directory. This vulnerability is fixed in 0.186.

Patch / fix

fixed in 1 distros 1

go github.com/daytonaio/daytona 0.186.0

govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 4 mo ago (2026-06-24)

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.2	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
GitHub	3.1	4.2	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
go	github.com/daytonaio/daytona	<0.186.0	0.186.0

Affected products

daytonaio daytona

Classification

Weakness

CWE-22 Improper Limitation of a Pathname to a Restricted Directory
CWE-250 Execution with Unnecessary Privileges
CWE-269 Improper Privilege Management
CWE-20 Improper Input Validation

References

github.com /daytonaio/daytona/security/advisories/GHSA-fjv8-j4p5-cr9m
web, advisory
nvd.nist.gov /vuln/detail/CVE-2026-54319
advisory
github.com /daytonaio/daytona
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary