# CVE-2026-54320: Daytona: Cross-tenant organization takeover via invitation acceptance with an unverified email

> Attackers can take over organizations by accepting invitations with unverified emails, gaining owner privileges in Daytona AI infrastructure.

- **Severity:** High 8.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-m6hx-cffh-3f3h

## What is CVE-2026-54320?

CVE-2026-54320 is a high-severity authentication bypass vulnerability in daytonaio daytona, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-54320?


## How do I fix CVE-2026-54320?

No fix has been published for CVE-2026-54320 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-54320 being exploited?

There is no known exploitation of CVE-2026-54320 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54320 and fix it if it is affected.

What it is: CVE-2026-54320 is a high-severity authentication bypass vulnerability in daytonaio daytona, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54320 in the wild and no public exploit code.

Affected product: daytonaio daytona. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54320/ (Markdown: https://insights.sbomify.com/CVE-2026-54320/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54320
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54320
- OSV: https://osv.dev/vulnerability/CVE-2026-54320

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54320/
Summaries are generated and may contain mistakes; the official description above is the record.