Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-fjv8-j4p5-cr9m

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

CVSS 4.2 MediumEPSS 0.0024 · 15th percentile

Published by the GitHub Advisory Database at 18 Jun 2026, 17:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/daytonaio/daytonaGo<0.186.00.186.0
Identifiers
GHSA-fjv8-j4p5-cr9m · CVE-2026-54319 · GO-2026-5367
Weakness (CWE)
CWE-20 · CWE-22 · CWE-250 · CWE-269
Tags
Published
18 Jun 2026
Updated
20 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Daytona versions before 0.186.0 (Go module github.com/daytonaio/daytona) could, in principle, let a sandbox volume reference containing path-traversal sequences resolve a bind-mount source outside the per-volume base directory. The source says this was not exploitable in any released version because the database validates volume references and rejects traversal input before any mount is built. Upgrade to 0.186.0 or later, which resolves volume references to canonical UUIDs and confines mount sources.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.2 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0024, the 15th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:05 UTC First seen by agentprime
  2. 31 Oct 2026, 15:05 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.