Skip to main content
VulnerabilityPublished Updated

CVE-2026-54321: daytonaio daytona · Insufficient Session Expiration

Affects daytonaio daytonaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.0 High : upgrade to 0.184.0 soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.184.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade daytona and daytonaio/daytona to 0.184.0.

Affected software

ProductAffectedFixed in
daytonaiodaytonaAffected
  • >=0.101.0 <0.184.0
Fixed in
  • 0.184.0
GitHubdaytonaio/daytonapkg:github/daytonaio/daytonaOther threatsAffected
  • <0.184.0 >=0.101.0
Fixed in
  • 0.184.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade daytona to version 0.184.0 or later where the vulnerability is fixed. Since the vendor advisory indicates the issue is resolved in 0.184.0, applying this official fix is the recommended remediation. No additional temporary mitigations are specified.

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.

References

Community reviews

Loading reviews…