Skip to main content

Daytona EUVDEUVD-2026-38565

| CVE-2026-54321 HIGH
Insufficient Session Expiration (CWE-613)
2026-06-16 https://github.com/daytonaio/daytona GHSA-ww63-pv5x-vfc8
7.0
CVSS 3.1 · Vendor: https://github.com/daytonaio/daytona
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Discover previously-public preview URL
  2. Delivery
    Wait for owner to set sandbox private
  3. Exploit
    Replay request to preview proxy
  4. Execution
    Hit stale cached 'public' decision
  5. Impact
    Read sandbox preview content anonymously

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V7 - Session Management Session expiration enforcement
Exploitation Conditions

Requires all of the following: (1) the target Daytona sandbox preview was previously set to public and the attacker obtained or guessed its preview URL while it was public; (2) the owner has just toggled that preview from public to private; (3) the request hits the preview proxy before the cached visibility state refreshes (bounded window, up to ~1 hour per advisory). Exploitation is limited to ordinary preview ports - terminal, toolbox, and recording-dashboard ports always require authentication and are not affected - and yields no cross-tenant access, privilege escalation, or code execution; high attack complexity (AC:H) reflects the timing race and prior-knowledge requirement.

Impact

The CVSS 3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L scoring 7.0 reflects an internet-reachable, unauthenticated condition but with high attack complexity, which fits the race-against-cache-expiry nature of the bug - the attacker must already know (or guess) the preview URL of a sandbox that very recently transitioned from public to private. No EPSS, KEV, SSVC, or POC signals were provided, and the GitHub advisory tags 'RCE' and 'Privilege Escalation' directly conflict with the advisory body, which states the issue does not involve cross-tenant access, privilege escalation, or RCE - those tags appear to be miscategorized and should not drive prioritization. Realistic risk is moderate and narrowly scoped: it matters most to Daytona operators whose users rely on the public-to-private toggle as a security boundary for sensitive in-progress work, and exposure ends as soon as the cache refreshes or the instance is upgraded.

Exploit ScenarioDerived

An attacker who already knows the URL of a Daytona sandbox preview that was recently public - for example one shared in a chat, demo, or commit - repeatedly polls that URL after the owner switches it to private, and continues to receive unauthenticated responses with potentially sensitive in-development content until the proxy's cached visibility state refreshes (up to roughly an hour per the advisory title). No public exploit is identified at time of analysis; exploitation is opportunistic rather than a remote takeover.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 16, 2026

Stale authorization caching in Daytona's preview proxy allows unauthenticated access to sandbox previews for a bounded window after their owner switches visibility from public back to private. The flaw affects versions 0.101.0 through 0.183.0 and is limited to ordinary preview ports - terminal, toolbox, and recording-dashboard ports remained protected. No public exploit identified at time of analysis, and the GitHub advisory tags suggesting RCE/Privilege Escalation contradict the advisory's own impact statement, which explicitly rules both out.

RemediationAI

Vendor-released patch: upgrade to Daytona v0.184.0 or later, in which visibility changes synchronously invalidate the proxy's cached preview state so revocation takes effect on the next request (https://github.com/daytonaio/daytona/security/advisories/GHSA-ww63-pv5x-vfc8). The vendor explicitly states there is no configuration workaround for earlier versions. As compensating controls until upgrade, operators can place the preview proxy behind a network-level allowlist or SSO/identity-aware proxy (this breaks anonymous public-preview sharing, which is the intended feature), or instruct users to delete and recreate sandboxes rather than toggle visibility (this loses sandbox state but guarantees immediate URL change), or shorten the proxy's visibility cache TTL if the deployment exposes that knob (reduces the exposure window at the cost of more control-plane lookups).

Affected VersionsENISA

daytona 0.101.0, < 0.184.0

Affected Packages

go github.com/daytonaio/daytona fix: 0.184.0
euvd daytona_0_101_0 fix: 0.184.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in go, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Daytona is an open-source development environment platform (Go package github.com/daytonaio/daytona) that runs user 'sandboxes' and exposes their HTTP preview ports through a proxy. The proxy caches each sandbox's visibility state (public vs. private) to avoid per-request lookups against the control plane. The root cause maps to CWE-613 (Insufficient Session Expiration): when an owner toggled visibility from public to private, the cached 'public' decision continued to authorize anonymous requests until the cache entry naturally expired (per the GHSA title, up to one hour), instead of being invalidated synchronously on the visibility change.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (https://github.com/daytonaio/daytona) PRIMARY 7.0 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L
vuln.today AI 3.7 LOW

Network-reachable and unauthenticated (AV:N/PR:N/UI:N) but requires timing race and prior knowledge of a previously-public URL (AC:H); only confidentiality of preview content is affected (C:L, I:N, A:N).

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
SUSE HIGH

Primary rating from Vendor (https://github.com/daytonaio/daytona).

CVSS VectorVendor: https://github.com/daytonaio/daytona

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

DescriptionCVE.org

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 the next request.

Workarounds

Upgrade to v0.184.0 or later. There is no configuration workaround for earlier versions.

Credit

Reported through Daytona's Vulnerability Disclosure Program by mrknightnidu(nidalkhan). Linkedin: https://www.linkedin.com/in/mrknight-nidu-031340328/

Executive ViewAI

Why It Matters

Daytona versions 0.101.0-0.183.0 contain a stale authorization cache vulnerability that allows unauthenticated access to privately-owned sandbox preview environments for a bounded period after visibility is changed from public to private. This creates a time-limited exposure window for any sensitive code, credentials, or data stored in live previews. Organizations should assess the typical contents of preview environments to determine if proprietary or regulated information could be accessed.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Enforce immediate invalidation of preview URLs when visibility changes; (2) restrict preview access to VPN/internal IP ranges; (3) enable logging for all preview endpoint access; (4) advise teams to exclude production credentials, API keys, and PII from preview environments; (5) configure alerts for anomalous preview access; (6) temporarily disable public-to-private visibility toggles until patch is available.

Threat Intelligence Overview

EPSS Score
0.2%
Top 84% exploitable
Threat Intel
1
1 source
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Server 16.1 Affected
SUSE Linux Enterprise Server for SAP applications 16.1 Affected
SUSE Linux Enterprise Module for Package Hub 15 SP5 Affected
SUSE Linux Enterprise Module for Package Hub 15 SP6 Affected
openSUSE Leap 15.5 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy