Daytona: Public sandbox previews remain accessible for up to one hour after being made private

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.0 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L

EPSS

• CVE-2026-54321: 0.40% estimated exploitation activity in the next 30 days; percentile 34.11 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Sandbox previews that were switched from public to private could remain reachable without authentication for a short period after the change, due to a cached visibility state that was not invalidated when the sandbox's visibility changed. Impact When a sandbox owner changed a preview from public to private, the preview proxy could continue serving unauthenticated requests to that sandbox's ordinary preview ports for a bounded period before the change took effect. Only sandboxes that had been made public and were later set back to private were affected, and only until the proxy's cached visibility state was refreshed. Terminal, toolbox, and recording-dashboard ports were never affected, as those always require authentication. The issue did not involve cross-tenant access, privilege escalation, or remote code execution. Patches Fixed in v0.184.0. Sandbox visibility changes now invalidate the proxy's cached preview state immediately, so revoking a public preview takes effect on…

Published by the source

16 Jun 2026, 21:05 UTC

Last modified by the source

20 Jul 2026, 21:14 UTC

Source last checked

26 Oct 2026, 15:25 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-ww63-pv5x-vfc8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54321

Advisory: Daytona: Public sandbox previews remain accessible for up to one hour after being made private
IDs: CVE-2026-54321, GHSA-ww63-pv5x-vfc8
Record: https://patchnext.com/advisories/cve-2026-54321 (revision 1, source checked 26 Oct 2026, 15:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/daytonaio/daytona 0.184.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/daytonaio/daytona: affected >= 0.101.0, <= 0.183.0; fixed in 0.184.0

## Suggested inspection (read-only)
- Go github.com/daytonaio/daytona: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/daytonaio/daytona.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-ww63-pv5x-vfc8 (GitHub-reviewed advisory GHSA-ww63-pv5x-vfc8 lists affected ranges: Go github.com/daytonaio/daytona >=0.101.0 <=0.183.0)

Commands are suggestions: review each one before running it.