dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-54324

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Daytona is a secure and elastic infrastructure runtime for AI-generated code execution and agent workflows. Prior to 0.185.0, a cross-tenant authorization flaw in Daytona's notification WebSocket gateway allowed any authenticated user to subscribe to another organization's realtime notification channel and passively receive that organization's events. This vulnerability is fixed in 0.185.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A cross-tenant authorization bypass vulnerability in Daytona's WebSocket notification gateway allowed any authenticated user to subscribe to another organization's realtime notification channel. This enabled passive interception of events from other tenants, exposing potentially sensitive organizational data through the WebSocket subscription mechanism.

MitigationUpgrade Daytona to version 0.185.0 or later to remediate the cross-tenant authorization flaw in the WebSocket notification gateway.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Daytona version
    Locate the Daytona's version file, binary, or use the CLI command to retrieve the version (e.g., daytona version, or inspect the installed package metadata)
    Affected if The installed version is lower than 0.185.0
  2. Verify the WebSocket notification gateway is active
    Check if the WebSocket notification gateway module is enabled in Daytona's configuration files or running services
    Affected if The WebSocket notification gateway feature is enabled and running
  3. Confirm multi-tenant organization configuration exists
    Review the Daytona deployment to confirm it is configured with multiple tenant organizations
    Affected if Daytona is deployed in a multi-tenant mode with more than one organization
  4. Inspect WebSocket subscription authorization
    Analyze the WebSocket notification gateway settings or test subscribing to a different organization's channel using an authenticated session from another tenant
    Affected if The system permits a user from one tenant to subscribe to another tenant's notification channel without proper authorization checks

You are affected if Daytona is installed with a version below 0.185.0 and the WebSocket notification gateway is enabled in a multi-tenant deployment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Daytona to version 0.185.0 or later to remediate the cross-tenant authorization flaw in the WebSocket notification gateway.

Recommended fix High confidence

0.185.0

  1. 1. Identify the current Daytona version deployed in your environment using `daytona version` or checking your deployment manifests
  2. 2. If running a version prior to 0.185.0, upgrade to version 0.185.0 or later
  3. 3. For containerized deployments, update the container image tag to the fixed release (e.g., `daytona/server:0.185.0`)
  4. 4. For package installations, run the appropriate package manager update command for your installation method
  5. 5. Restart the Daytona services to apply the update
  6. 6. Verify the upgrade was successful by checking the version with `daytona version`
  7. 7. Test that the WebSocket notification gateway correctly enforces tenant isolation by attempting to subscribe to a different organization's channel (this should fail)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54324 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54324 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data