CVE-2026-54319
Deferred Deferred - Pending Action
Path Traversal in Daytona Infrastructure Runtime

Publication date: 2026-06-23

Last updated on: 2026-06-23

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-23
Last Modified
2026-06-23
Generated
2026-06-24
AI Q&A
2026-06-23
EPSS Evaluated
N/A
NVD
CVE-2026-54319
EUVD
EUVD-2026-38564
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
daytonaio daytona to 0.186 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-269 The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
CWE-250 The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Detection Guidance

This vulnerability involves a sandbox volume reference path traversal issue in the Daytona project, where volume references could potentially be used to escape the intended directory confinement.

However, the vulnerability was not exploitable in any released versions due to validation checks that reject path-traversal sequences before any mount is constructed.

No specific detection commands or network/system scanning methods are provided in the available resources.

Mitigation Strategies

To mitigate this vulnerability, users are advised to upgrade Daytona to version 0.186.0 or later.

The fix involves resolving volume references to canonical UUIDs server-side before they reach the runner, ensuring the mount source remains confined to the volume base directory.

Impact Analysis

If exploitable, this vulnerability could allow an authenticated user to read and write data outside their designated sandbox volume, potentially accessing or modifying other tenants' volume data. This could lead to unauthorized data exposure or data corruption.

However, in practice, the vulnerability was not exploitable in released versions due to validation checks. The severity is rated as Medium (CVSS score 4.2), reflecting the potential impact if the vulnerability were reachable.

Users are advised to upgrade to version 0.186.0 or later to fully mitigate this risk.

Executive Summary

CVE-2026-54319 is a sandbox volume reference path traversal vulnerability in the Daytona project. The issue arises because a volume reference (either a volume ID or name) was used to build a host bind-mount source path without proper confinement. This means that if the reference contained path-traversal sequences, it could potentially resolve the mount source outside the intended per-volume base directory.

Although this vulnerability could allow an authenticated user to access data outside their allowed volume, it was not exploitable in any released versions due to validation checks that reject path-traversal sequences before any mount is constructed. The problem was fixed in version 0.186.0 by resolving volume references to canonical UUIDs server-side, ensuring the mount source remains confined.

Compliance Impact

The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-54319. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart