CVE-2026-54324: daytonaio daytona · Insecure Direct Object Reference
Affects daytonaio daytonaSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 0.185.0 when convenient.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.185.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 23 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.185.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| daytonaiodaytona | Affected
| Fixed in
|
GitHubdaytonaio/daytonapkg:github/daytonaio/daytonaOther threats | Affected
| Fixed in
|
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.185.0 or later, where this authorization bypass vulnerability is fixed. Patch status is not explicitly stated as 'official-fix' in the vendor advisory, but the description confirms the issue is resolved in 0.185.0. No additional mitigations are indicated.
Description
Daytona is a secure and elastic infrastructure runtime for AI-generated code execution and agent workflows. Prior to 0.185.0, a cross-tenant authorization flaw in Daytona's notification WebSocket gateway allowed any authenticated user to subscribe to another organization's realtime notification channel and passively receive that organization's events. This vulnerability is fixed in 0.185.0.