Skip to main content
VulnerabilityPublished

CVE-2026-54320: daytonaio daytona · Improper Authentication

Affects daytonaio daytonaSource CVE Database V5

0
Compare

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

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% 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:L/UI:N/S:C/C:H/I:H/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.184.0
Fixed in
  • 0.184.0
GitHubdaytonaio/daytonapkg:github/daytonaio/daytonaOther threatsAffected
  • <0.184.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 by enforcing email verification on invitation acceptance. No other mitigations are specified. Patch status is confirmed fixed in 0.184.0.

Description

Daytona is a secure and elastic infrastructure runtime for AI-generated code execution and agent workflows. Prior to 0.184.0, organization invitations could be accepted (and declined) by a user whose email matched the invitation but had not been verified. Daytona authenticates users via OIDC and matches an invitation's target email against the email in the caller's token, but the invitation accept and decline paths did not require that email to be verified, unlike organization creation, which already enforced verification. On identity providers that allow self-service signup and issue a session before the email is verified, an actor could register an address matching a pending invitation, leave it unverified, and accept the invitation, joining the target organization with the role the invitation carried (up to Owner). This vulnerability is fixed in 0.184.0.

References

Community reviews

Loading reviews…