Authentication Bypass in Daytona (CVE-2026-54320)
Summary
Authentication bypass in Daytona (CVE-2026-54320). Confidential information can be exposed externally. Mitigation: upgrade to 0.184.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54320 has been found in Daytona.
Confidential information can be exposed externally. CVSS score: 8.4/10.
What to do: upgrade Daytona to 0.184.0 or later.
If unsure, ask your IT team or search "Daytona CVE-2026-54320" on the vendor's site.
CVE-2026-54320 (Daytona) — CWE-287 / CVSS v3 8.4
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.184.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in Daytona.
Check the vendor advisory for the affected versions of Daytona.
Severity: High (CVSS 8.4/10). Confidential information can be exposed externally.
Update to 0.184.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Daytona' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Daytona' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Daytonaを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Daytona to 0.184.0ステージング環境で 0.184.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov