Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Daytona versions before 0.185.0 (the Go module github.com/daytonaio/daytona) let an authenticated user who owns any organization modify or delete a role belonging to a different organization, provided they know that role's identifier. An attacker could overwrite the role's permissions, which would change access for every member and API key holding it, or delete the role. Upgrade to 0.185.0 or later; no workaround is given, and the source notes single-organization self-hosted deployments are not exploitable.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.7 | High | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0030, the 23rd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:05 UTC First seen by agentprime
- 31 Oct 2026, 15:05 UTC Confirmed by OSV