Quick answers
- Is CVE-2026-54321 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54321 being exploited in the wild.
- How severe is CVE-2026-54321?
- High severity, with a CVSS score of 7, published 23 June 2026.
- Which products and versions are affected?
- Daytona >= 0.101.0, < 0.184.0, >= 0.101.0, <= 0.183.0; github.com/daytonaio/daytona (Go) >= 0.101.0, <= 0.183.0, SEMVER:introduced=0.101.0,fixed=0.184.0.
- Is there a fix for CVE-2026-54321?
- Yes. github.com/daytonaio/daytona (Go): upgrade to 0.184.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54321 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-54321?
- Check whether you run Daytona or github.com/daytonaio/daytona (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/daytonaio/daytona (Go): upgrade to 0.184.0 or later
go get github.com/daytonaio/daytona@v0.184.0
Technical details
An authorization bypass exists in Daytona's preview proxy due to insufficient cache invalidation. When a sandbox's visibility is changed from public to private, the proxy continues to serve unauthenticated requests based on a cached 'public' state for a bounded period (up to one hour). The vulnerability is limited to ordinary preview ports; terminal, toolbox, and dashboard ports are unaffected as they always require authentication. Attackers can exploit this by accessing the preview URL of a sandbox that was recently made private. The issue is resolved in version 0.184.0, which ensures visibility changes immediately invalidate the proxy's cached state.
Affected products
- daytonaio daytona >= 0.101.0, < 0.184.0
Identifiers
- CVE-2026-54321
- GHSA-ww63-pv5x-vfc8
- GO-2026-5729
Timeline
- 2026-06-05: advisory: GitHub Security Advisory published
- 2026-06-23: disclosed: NVD publication date
- 2026-06-23: patched: Fix released in version 0.184.0