CVE-2026-54319: Daytona path traversal in sandbox volume host mount construction

CVE-2026-54319 · Severity: medium · CVSS 4.2 · Published 2026-06-23

Daytona is a platform used to run AI-generated code and automated agent workflows in secure, isolated environments. A vulnerability was identified where the system did not properly restrict how storage volumes were mapped to the host server, which could theoretically allow a user to access data belonging to other users. However, because the system validates these requests against a database using strict ID formats, the issue was not exploitable in any released versions.

Technologies: Daytona, github.com/daytonaio/daytona (Go). Vendors: Daytona, Go.

Quick answers

Is CVE-2026-54319 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-54319 being exploited in the wild.
How severe is CVE-2026-54319?
Medium severity, with a CVSS score of 4.2, published 23 June 2026.
Which products and versions are affected?
Daytona < 0.186.0; github.com/daytonaio/daytona (Go) <= 0.185.0, SEMVER:introduced=0,fixed=0.186.0.
Is there a fix for CVE-2026-54319?
Yes. github.com/daytonaio/daytona (Go): upgrade to 0.186.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54319 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-54319?
Check whether you run Daytona or github.com/daytonaio/daytona (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/daytonaio/daytona (Go): upgrade to 0.186.0 or later
    go get github.com/daytonaio/daytona@v0.186.0

Technical details

A path traversal vulnerability exists in Daytona's runner component where a sandbox volume reference (volumeId) was used to construct host bind-mount source paths without proper confinement. An attacker could theoretically use traversal sequences to mount host paths outside the intended per-volume directory, potentially leading to cross-tenant data access. In practice, the vulnerability was not exploitable in released versions because the volumeId is validated against a database as a UUID before reaching the runner, causing traversal payloads to fail validation. The fix in version 0.186.0 ensures volume references are resolved to canonical UUIDs server-side and that the runner strictly confines mount sources to the volume base directory.

Affected products

  • Daytona Daytona < 0.186.0

Identifiers

  • CVE-2026-54319
  • GHSA-fjv8-j4p5-cr9m
  • GO-2026-5367

Timeline

  • 2026-06-17: advisory: GitHub Security Advisory published
  • 2026-06-23: disclosed: CVE published to NVD
  • 2026-06-23: patched: Fix released in version 0.186.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.