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

> Attackers can mount arbitrary host paths into sandboxes via path traversal in volume IDs, enabling cross-tenant data access and host escape.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-fjv8-j4p5-cr9m, GO-2026-5367

## What is CVE-2026-54319?

CVE-2026-54319 is a medium-severity path traversal vulnerability in daytonaio daytona, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-269 (Improper Privilege Management), CWE-250 (Execution with Unnecessary Privileges), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-54319?

3 open source packages ship an affected version, including github.com/daytonaio/daytona.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/daytonaio/daytona` | Go | All versions | 0.186.0 |
| `github.com/daytonaio/daytona` | Go | All versions | 0.186.0 |
| `github.com/daytonaio/daytona` | Go | All versions | 0.186.0 |

## How do I fix CVE-2026-54319?

Upgrade github.com/daytonaio/daytona to 0.186.0 or later.

## Is CVE-2026-54319 being exploited?

There is no known exploitation of CVE-2026-54319 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54319 and fix it if it is affected.

What it is: CVE-2026-54319 is a medium-severity path traversal vulnerability in daytonaio daytona, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54319 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/daytonaio/daytona (Go): affected all versions; fixed in 0.186.0
- github.com/daytonaio/daytona (Go): affected all versions; fixed in 0.186.0
- github.com/daytonaio/daytona (Go): affected all versions; fixed in 0.186.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54319/ (Markdown: https://insights.sbomify.com/CVE-2026-54319/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54319
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54319
- OSV: https://osv.dev/vulnerability/CVE-2026-54319

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54319/
Summaries are generated and may contain mistakes; the official description above is the record.