Vulnerability in github.com/daytonaio/daytona (CVE-2026-54322)
Summary
Vulnerability in github.com/daytonaio/daytona (CVE-2026-54322). Data can be tampered with by attackers. 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, Daytona's organization role update and delete endpoints authorized the caller as an owner of the organization named in the request path, but resolved and mutated the target role by its identifier alone, without verifying the role belonged to that organization. An authenticated user who owns any organization (organizations are self-service) could therefore modify the permissions of, or delete, a role belonging to a different organization, given that role's identifier. This vulnerability is fixed in 0.185.0.
Source: GitHub Security Advisories (Global) 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-54322 has been found in github.com/daytonaio/daytona.
Data can be tampered with by attackers. CVSS score: 7.7/10.
What to do: upgrade github.com/daytonaio/daytona to 0.185.0 or later.
If unsure, ask your IT team or search "github.com/daytonaio/daytona CVE-2026-54322" on the vendor's site.
CVE-2026-54322 (github.com/daytonaio/daytona) — CWE-639 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.185.0 — apply immediately
Workaround: None.
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-639) exists in github.com/daytonaio/daytona.
Check the vendor advisory for the affected versions of github.com/daytonaio/daytona.
Severity: High (CVSS 7.7/10). Data can be tampered with by attackers.
Update to 0.185.0.
Workaround: None.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
None.パッチが適用されるまでの応急処置として、None. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/daytonaio/daytona to 0.185.0ステージング環境で 0.185.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com