CVE-2026-54322: Daytona IDOR in organization role update and delete endpoints

CVE-2026-54322 · Severity: high · CVSS 7.7 · Published 2026-06-23

Daytona is a platform used to manage secure environments for AI-generated code and automated workflows. A security flaw allowed users who manage their own organization to modify or delete administrative roles belonging to other organizations on the same platform. If exploited, this could allow an attacker to disrupt operations, strip permissions from legitimate users, or escalate their own privileges within a victim's environment.

Technologies: Daytona, github.com/daytonaio/daytona (Go). Vendors: Daytona, Go.

Quick answers

Is CVE-2026-54322 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-54322 being exploited in the wild.
How severe is CVE-2026-54322?
High severity, with a CVSS score of 7.7, published 23 June 2026.
Which products and versions are affected?
Daytona < 0.185.0, <= 0.184.0; github.com/daytonaio/daytona (Go) <= 0.184.0, SEMVER:introduced=0,fixed=0.185.0.
Is there a fix for CVE-2026-54322?
Yes. github.com/daytonaio/daytona (Go): upgrade to 0.185.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54322 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-54322?
Check whether you run Daytona or github.com/daytonaio/daytona (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/daytonaio/daytona (Go): upgrade to 0.185.0 or later
    go get github.com/daytonaio/daytona@v0.185.0

Technical details

An Insecure Direct Object Reference (IDOR) vulnerability exists in Daytona's organization role management endpoints. While the application validates that a caller is an owner of the organization specified in the request path, it resolves the target role for update or delete operations using only the role's unique identifier without verifying that the role actually belongs to the caller's organization. An authenticated attacker with owner privileges over any organization can exploit this to modify or delete roles in other organizations, provided they know the target role's identifier. This can lead to privilege escalation, denial of service for legitimate users, and limited information disclosure of role permissions. The issue is fixed in version 0.185.0 by scoping role lookups to the caller's organization.

Affected products

  • Daytona Daytona < 0.185.0

Identifiers

  • CVE-2026-54322
  • GHSA-qxvm-pcfm-qc39
  • GO-2026-5600

Timeline

  • 2026-06-09: advisory: GitHub advisory published
  • 2026-06-23: disclosed: NVD publication date
  • 2026-06-23: patched: Fix released in version 0.185.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.