CVE-2026-54319 daytonaio CVE debrief

Who should care

Security teams and administrators responsible for AI-generated code execution and agent workflows using Daytona infrastructure runtime should be aware of this vulnerability. They should assess their exposure and take necessary steps to upgrade to version 0.186 or apply compensating controls to mitigate potential risks.

Technical summary

The vulnerability exists in the way Daytona handles sandbox volume references. A volume reference, which can be a volume ID or name, is forwarded to the runner and used to construct the host bind-mount source path without proper confinement. This allows a potential attacker to use path-traversal sequences to resolve the mount source outside the intended per-volume base directory. The CVSS vector for this vulnerability is CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N, indicating a Medium severity level. The weakness types associated with this vulnerability are CWE-22, CWE-250, and CWE-269.

Defensive priority

Medium priority should be given to addressing this vulnerability, as it has a Medium CVSS score and could potentially be used in targeted attacks. However, the attack complexity is High, which may limit the immediate risk.

Recommended defensive actions

• Upgrade Daytona to version 0.186 or later to fix the vulnerability.
• Review and restrict access to sandbox volume references to prevent unauthorized usage.
• Implement additional monitoring and logging to detect potential path-traversal attacks.
• Conduct a thorough inventory of Daytona installations and assess exposure to this vulnerability.
• Consider applying compensating controls, such as stricter access controls or anomaly detection, until an upgrade can be performed.

Evidence notes

The evidence for this vulnerability comes from the NVD and CVE.org records. The CVE record was published on June 23, 2026, and modified on June 24, 2026. The NVD detail page provides additional information about the vulnerability, including its CVSS score and vector. A security advisory from GitHub also provides context about the vulnerability and its fix.

Official resources