Daytona EUVD-2026-38564

Exploitation requires an authenticated Daytona user account (CVSS PR:L) with permission to create or reference sandbox volumes. The attack targets the runner's bind-mount path construction by supplying a volume reference containing path-traversal sequences. On all released versions (<= 0.185.0), exploitation is prevented by a structural constraint: the volumeId database column is a UUID type, which rejects any string containing traversal characters at database validation time, before the runner is ever invoked. This means the vulnerability is only theoretically reachable in a hypothetical implementation where that UUID validation is absent or bypassed - a condition the vendor states did not exist in any released build. What limits exploitation: (1) mandatory authentication eliminates unauthenticated attack surface; (2) UUID database column type structurally blocks traversal payloads on all released versions; (3) no released build allowed a traversal sequence to reach the runner layer. The vulnerability is not exploitable under default or non-default configuration of any released Daytona version.

The CVSS 3.1 score of 4.2 (Medium) encodes network attack vector (AV:N), high complexity (AC:H), low-privilege authentication (PR:L), no user interaction (UI:N), unchanged scope (S:U), and limited confidentiality and integrity impact (C:L/I:L). AC:H accurately reflects the practical reality: exploitation would require bypassing the UUID database validation, which the vendor states was not achievable in testing on any released build. EPSS data is absent from available intelligence, so probability-of-exploitation quantification is unavailable. The vulnerability is not listed in CISA KEV and no public proof-of-concept has been identified, both consistent with a theoretical flaw in unreachable code. The theoretical worst-case - cross-tenant volume data access in a multi-tenant hosted environment - is a meaningful impact class, but the vendor's explicit statement that no released version was exploitable, corroborated by the structural UUID constraint, substantially reduces real-world priority. This is a defense-in-depth gap that warrants patching on schedule, not emergency response.

An authenticated Daytona user submits a sandbox volume mount request with a volumeId or volume name containing path-traversal sequences (e.g., a name like '../../sensitive-tenant-volume') targeting the runner's bind-mount path construction. On all released versions <= 0.185.0, the database validation layer rejects the non-UUID reference before it reaches the runner, returning a server-side validation error and constructing no mount - the attack terminates at input validation. No public proof-of-concept exploit has been identified, and the vendor could not reproduce cross-tenant access or an out-of-base mount on any released build.