# CVE-2026-54322: Daytona: Cross-org IDOR in organization role update/delete — any org owner can rewrite or destroy another org's roles

> Authenticated organization owners can modify or delete roles in other organizations due to missing ownership checks, enabling privilege escalation and data modification.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-qxvm-pcfm-qc39, GO-2026-5600

## What is CVE-2026-54322?

CVE-2026-54322 is a high-severity missing authorization vulnerability in daytonaio daytona, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-54322?

3 open source packages ship an affected version, including github.com/daytonaio/daytona.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/daytonaio/daytona` | Go | All versions | 0.185.0 |
| `github.com/daytonaio/daytona` | Go | All versions | 0.185.0 |
| `github.com/daytonaio/daytona` | Go | All versions | 0.185.0 |

## How do I fix CVE-2026-54322?

Upgrade github.com/daytonaio/daytona to 0.185.0 or later.

## Is CVE-2026-54322 being exploited?

There is no known exploitation of CVE-2026-54322 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54322 and fix it if it is affected.

What it is: CVE-2026-54322 is a high-severity missing authorization vulnerability in daytonaio daytona, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54322 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/daytonaio/daytona (Go): affected all versions; fixed in 0.185.0
- github.com/daytonaio/daytona (Go): affected all versions; fixed in 0.185.0
- github.com/daytonaio/daytona (Go): affected all versions; fixed in 0.185.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54322/ (Markdown: https://insights.sbomify.com/CVE-2026-54322/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54322
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54322
- OSV: https://osv.dev/vulnerability/CVE-2026-54322

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54322/
Summaries are generated and may contain mistakes; the official description above is the record.