Vulnerabilities in pkg:golang/github.com/daytonaio/daytona

PACKAGE
Advisory Identifier: GHSA-fjv8-j4p5-cr9m
Advisory Summary

CVE-2026-54319 is a MODERATE (CVSS 4.2) path traversal vulnerability (CWE-269: Improper Privilege Management) affecting Daytona libraries in the Go ecosystem. The issue involves path traversal in sandbox volume id mounts arbitrary host paths into the sandbox — cross-tenant data access and host escape. Remediation is available by upgrading affected packages to version 0.186.0.

4 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/daytonaio/daytona

4 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/daytonaio/daytona. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-fjv8-j4p5-cr9m CVE-2026-54319 MODERATE Daytona: Path traversal in sandbox volume id mounts arbitrary host paths into the sandbox — cross-tenant data access and host escape
GHSA-qxvm-pcfm-qc39 CVE-2026-54322 HIGH Daytona: Cross-org IDOR in organization role update/delete — any org owner can rewrite or destroy another org's roles
GHSA-ww63-pv5x-vfc8 CVE-2026-54321 HIGH Daytona: Public sandbox previews remain accessible for up to one hour after being made private
GHSA-qwxf-2m7m-2m3x CVE-2026-54324 MODERATE Daytona: Cross-tenant data leak in notification WebSocket gateway via unverified organizationId join

CVE-2026-54319 at a Glance

CVE Identifier CVE-2026-54319
GHSA Identifier GHSA-fjv8-j4p5-cr9m
Severity MODERATE
CVSS v3.1 Base Score 4.2
CWE Classification CWE-269: Improper Privilege Management
Affected Product Daytona
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 4.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-54319

To remediate this vulnerability, upgrade all affected Daytona dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/daytonaio/daytona fixed: 0.186.0
Upgrade github.com/daytonaio/daytona to 0.186.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/daytonaio/daytona

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-54319, inspect your project dependencies for Daytona:

inspect dependencies for github.com/daytonaio/daytona

Analyze the terminal output to locate any version of Daytona in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.186.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-269: Improper Privilege Management, where the product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. In Daytona, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary 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. ## Impact Had the traversal been reachable, an authenticated user could have caused the runner to bind-mount an unintended host path into their sandbox, with a worst-case impact of read and write access to other tenants' volume data (per-volume FUSE mounts are world-readable and writable). Important: this path was not exploitable in any released version. A volume reference is validated against the database before it reaches the runner, and the volume id column is a UUID type, so a reference containing traversal sequences is rejected at validation time and the request fails before any mount is constructed. We could not reproduce cross-tenant access or an out-of-base host mount on a released build; the observable effect of the documented payload was a server-side validation error. Severity is assessed as Medium on that basis. ## Patches Fixed in v0.186.0. Volume references are now resolved to the canonical volume UUID server-side before reaching the runner, so a name can never flow downstream as a path component, and the runner confines the mount source to the volume base directory and rejects any non-UUID reference. ## Workarounds Upgrade to v0.186.0 or later. No configuration workaround is required for released versions, which were not exploitable. ## Credit Reported by @vnth4nhnt from CyStack.

CVE-2026-54319 Affected Daytona Versions

1 component(s)
Fixed Versions:
0.186.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/daytonaio/daytona
Go
< 0.186.0
0.186.0

References

Frequently Asked Questions

What is CVE-2026-54319?
CVE-2026-54319 is a security vulnerability in Daytona involving Path traversal in sandbox volume id mounts arbitrary host paths into the sandbox — cross-tenant data access and host escape under CWE-269: Improper Privilege Management.
Which Daytona versions are affected?
Affected versions include releases prior to 0.186.0 across affected packages: github.com/daytonaio/daytona.
What version fixes CVE-2026-54319?
Upgrading to 0.186.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/daytonaio/daytona affected?
Yes, github.com/daytonaio/daytona is affected in releases prior to 0.186.0. Upgrade your dependency to 0.186.0 or later.
What is the CVSS score of CVE-2026-54319?
CVE-2026-54319 has a CVSS v3.1 base score of 4.2 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N.
What CWE is associated with CVE-2026-54319?
CVE-2026-54319 is classified under CWE-269: Improper Privilege Management (The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.).
How can I check Go dependencies for CVE-2026-54319?
Run the dependency tree command: 'inspect dependencies for github.com/daytonaio/daytona'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fjv8-j4p5-cr9m",
  "modified" : "2026-07-20T21:15:16Z",
  "published" : "2026-06-18T17:19:51Z",
  "aliases" : [ "CVE-2026-54319" ],
  "summary" : "Daytona: Path traversal in sandbox volume id mounts arbitrary host paths into the sandbox — cross-tenant data access and host escape",
  "details" : "## Summary\nA sandbox volume reference (`volumeId`, which may also be a volume name) was forwarded to the\nrunner and used to build the host bind-mount source path without confinement. A reference\ncontaining path-traversal sequences could in principle resolve the mount source outside the\nintended per-volume base directory.\n\n## Impact\nHad the traversal been reachable, an authenticated user could have caused the runner to\nbind-mount an unintended host path into their sandbox, with a worst-case impact of read and\nwrite access to other tenants' volume data (per-volume FUSE mounts are world-readable and\nwritable).\n\nImportant: this path was not exploitable in any released version. A volume reference is\nvalidated against the database before it reaches the runner, and the volume id column is a\nUUID type, so a reference containing traversal sequences is rejected at validation time and\nthe request fails before any mount is constructed. We could not reproduce cross-tenant access\nor an out-of-base host mount on a released build; the observable effect of the documented\npayload was a server-side validation error. Severity is assessed as Medium on that basis.\n\n## Patches\nFixed in v0.186.0. Volume references are now resolved to the canonical volume UUID\nserver-side before reaching the runner, so a name can never flow downstream as a path\ncomponent, and the runner confines the mount source to the volume base directory and rejects\nany non-UUID reference.\n\n## Workarounds\nUpgrade to v0.186.0 or later. No configuration workaround is required for released versions,\nwhich were not exploitable.\n\n## Credit\nReported by @vnth4nhnt from CyStack.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/daytonaio/daytona"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.186.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.185.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/daytonaio/daytona/security/advisories/GHSA-fjv8-j4p5-cr9m"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-54319"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/daytonaio/daytona"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20", "CWE-22", "CWE-250", "CWE-269" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-18T17:19:51Z",
    "nvd_published_at" : "2026-06-23T19:17:07Z"
  }
}