# CVE-2026-54321: Daytona: Public sandbox previews remain accessible for up to one hour after being made private

> Attackers can access private sandbox previews without authentication for up to one hour after visibility changes due to cached state issues.

- **Severity:** High 7.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-ww63-pv5x-vfc8, GO-2026-5729

## What is CVE-2026-54321?

CVE-2026-54321 is a high-severity missing authorization vulnerability in daytonaio daytona, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Daytona is a secure and elastic infrastructure runtime for AI-generated code execution and agent workflows. From 0.101.0 until 0.184.0, 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. This vulnerability is fixed in 0.184.0.

Weakness: CWE-863 (Incorrect Authorization), CWE-613 (DEPRECATED: Insufficient Session Expiration)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/daytonaio/daytona` | Go | From 0.101.0 | 0.184.0 |
| `github.com/daytonaio/daytona` | Go | From 0.101.0 | 0.184.0 |
| `github.com/daytonaio/daytona` | Go | From 0.101.0 | 0.184.0 |

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

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

## Is CVE-2026-54321 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54321 is a high-severity missing authorization vulnerability in daytonaio daytona, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54321 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/daytonaio/daytona (Go): affected from 0.101.0; fixed in 0.184.0
- github.com/daytonaio/daytona (Go): affected from 0.101.0; fixed in 0.184.0
- github.com/daytonaio/daytona (Go): affected from 0.101.0; fixed in 0.184.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-54321/ (Markdown: https://insights.sbomify.com/CVE-2026-54321/index.md)
```

## Sources

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

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