Daytona: Cross-tenant organization takeover via invitation acceptance with an unverified email
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| daytonaio | daytona | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Daytonaio | Daytona |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.352% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Daytonaio
Daytonaio daytona |
|
| Vendors & Products |
Daytonaio
Daytonaio daytona |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Daytona: Cross-tenant organization takeover via invitation acceptance with an unverified email | |
| Weaknesses | CWE-287 CWE-863 |
|
| References |
| |
| Metrics |
cvssV3_1
|