Vulnerability in Daytona (CVE-2026-54323)
Summary
Vulnerability in Daytona (CVE-2026-54323). Confidential information can be exposed externally. Exploitable via Authorization header. Mitigation: upgrade to 0.185.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.185.0, the daemon's git clone implementation disabled TLS certificate verification. When a clone request carried Git credentials, the daemon sent the HTTP Basic Authorization header to the remote over a connection whose certificate was never validated, on both the go-git and native git CLI code paths. An attacker able to intercept clone traffic could present any TLS certificate, capture the Git credentials supplied for the clone, and serve tampered repository content into the sandbox. This vulnerability is fixed in 0.185.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-54323 has been found in Daytona.
Attackers can target a specific entry point like Authorization header over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade Daytona to 0.185.0 or later.
If unsure, ask your IT team or search "Daytona CVE-2026-54323" on the vendor's site.
CVE-2026-54323 (Daytona) — CWE-295 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Authorization header
Patched: 0.185.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.
A vulnerability (CWE-295) exists in Daytona. Attackers reach the vulnerable code path via Authorization header without authentication.
Check the vendor advisory for the affected versions of Daytona. Attack surface: Authorization header.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 0.185.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.185.0ステージング環境で 0.185.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