{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54320 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54320 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-54320 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-54320 in the wild and no public exploit code.\n\nAffected product: daytonaio daytona. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54320/ (Markdown: https://insights.sbomify.com/CVE-2026-54320/index.md)","id":"CVE-2026-54320","markdown":"https://insights.sbomify.com/CVE-2026-54320/index.md","name":"CVE-2026-54320","record":{"aliases":["GHSA-m6hx-cffh-3f3h"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"AI code execution runtime","requires_auth":"low_privilege","summary":"Attackers can take over organizations by accepting invitations with unverified emails, gaining owner privileges in Daytona AI infrastructure.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-287","name":"Improper Authentication"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Daytona: Cross-tenant organization takeover via invitation acceptance with an unverified email","id":"CVE-2026-54320","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Daytona: Public sandbox previews remain accessible for up to one hour after being made private","id":"CVE-2026-54321"},"packages":[],"prev":{"headline":"Daytona: Path traversal in sandbox volume id mounts arbitrary host paths into the sandbox — cross-tenant data access and host escape","id":"CVE-2026-54319"},"products":["daytona"],"published":"2026-06-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-24","vendors":["daytonaio"]},"summary":"Attackers can take over organizations by accepting invitations with unverified emails, gaining owner privileges in Daytona AI infrastructure.","url":"https://insights.sbomify.com/CVE-2026-54320/"}