← Back
CVE-2026-54321
high
CVSS 7.0
Vulnerability in github.com/daytonaio/daytona (CVE-2026-54321)
Summary
vulnerability in github.com/daytonaio/daytona (CVE-2026-54321). Confidential information can be exposed externally. Mitigation: upgrade to `0.184.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54321** has been found in github.com/daytonaio/daytona.
Confidential information can be exposed externally. CVSS score: 7.0/10.
What to do: upgrade github.com/daytonaio/daytona to **0.184.0** or later.
If unsure, ask your IT team or search "github.com/daytonaio/daytona CVE-2026-54321" on the vendor's site.
CVE-2026-54321 (github.com/daytonaio/daytona) — CWE-613 / CVSS v3 7.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `0.184.0` — apply immediately
Workaround: Upgrade to v0.184.0 or later.
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.
❓ What is the problem
**A vulnerability** (CWE-613) exists in github.com/daytonaio/daytona.
📍 Affected scope
github.com/daytonaio/daytona — .
🔥 Severity
Severity: High (CVSS 7.0/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.184.0**.
🛡️ Workaround
Workaround: Upgrade to v0.184.0 or later.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/daytonaio/daytona' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/daytonaio/daytona' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/daytonaio/daytona` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Upgrade to v0.184.0 or later.パッチが適用されるまでの応急処置として、Upgrade to v0.184.0 or later. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade github.com/daytonaio/daytona to 0.184.0ステージング環境で 0.184.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/daytonaio/daytona
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.184.0"}]}]