How severe is GHSA-qxvm-pcfm-qc39?

GHSA-qxvm-pcfm-qc39 has a CVSS score of 7.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-qxvm-pcfm-qc39?

GHSA-qxvm-pcfm-qc39 affects the following packages: github.com/daytonaio/daytona (Go). Ecosystems affected: Go.

How do I fix GHSA-qxvm-pcfm-qc39?

Update github.com/daytonaio/daytona to 0.185.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qxvm-pcfm-qc39 is resolved across your whole dependency graph.

How do I detect GHSA-qxvm-pcfm-qc39 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/daytonaio/daytona, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qxvm-pcfm-qc39 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-qxvm-pcfm-qc39 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qxvm-pcfm-qc39 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-qxvm-pcfm-qc39?

GHSA-qxvm-pcfm-qc39 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 21th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-qxvm-pcfm-qc39?

GHSA-qxvm-pcfm-qc39 is classified as CWE-639 (CWE-639), CWE-862 (CWE-862). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qxvm-pcfm-qc39 published, and has it been updated?

GHSA-qxvm-pcfm-qc39 was published on June 16, 2026 and was last updated on July 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

GHSA-qxvm-pcfm-qc39 — daytona

HIGH

GHSA-qxvm-pcfm-qc39 is a high-severity (CVSS 7.7) CWE-639 vulnerability in github.com/daytonaio/daytona. A fix is available for github.com/daytonaio/daytona — see the affected versions and patch details below.

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

Also known asCVE-2026-54322GO-2026-5600

Published

Jun 16, 2026

Updated

Jul 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-qxvm-pcfm-qc39.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs21th percentile — riskier than 21% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-qxvm-pcfm-qc39 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐹github.com/daytonaio/daytona

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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.

Impact

This is a cross-tenant broken access control (IDOR) issue affecting multi-tenant deployments, including the managed Daytona platform. Using a target role's identifier, an attacker with owner rights over their own organization could:

Overwrite the target role's name and permission set, escalating or stripping privileges for every member and API key in the victim organization that holds that role.
Delete the target role, removing the associated permissions from its holders.
Observe the victim role's current permission set returned in the update response (limited information disclosure).

Exploitation requires knowledge of the target role's identifier, which is not enumerable across organizations and is not exposed to non-members through the API.

Affected versions

All versions up to and including 0.184.0.

Patches

Fixed in 0.185.0. The role update, delete, and role-assignment lookups are now scoped to the caller's organization, so a role belonging to another organization resolves to "not found" before any read or mutation. The managed Daytona platform was updated on release of 0.185.0.

Workarounds

None. Upgrade to 0.185.0. Single-organization self-hosted deployments are not exploitable, as the issue requires a second organization to target.

Credit

Reported by @vnth4nhnt.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/daytonaio/daytona`	all versions	0.185.0`go get github.com/daytonaio/daytona@v0.185.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/daytonaio/daytona, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/daytonaio/daytona to 0.185.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qxvm-pcfm-qc39 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Summary 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. ### Impact This is a cross-tenant broken access control (IDOR) issue affecting multi-tenant deployments, including