Compliance Impact

This vulnerability allows any authenticated user to subscribe to another organization's real-time notification channel and passively receive sensitive events, resulting in a cross-tenant confidentiality breach.

Such unauthorized access to sensitive data could lead to violations of data protection regulations and standards like GDPR and HIPAA, which require strict controls on data confidentiality and access.

Therefore, exploitation of this flaw could compromise compliance with these regulations by exposing sensitive organizational data to unauthorized parties.

Useful 0 Not Useful 0

Executive Summary

CVE-2026-54324 is a cross-tenant authorization flaw in Daytona's notification WebSocket gateway affecting versions 0.101.0 to 0.184.0. This vulnerability allowed any authenticated user to subscribe to another organization's real-time notification channel by providing an unverified organization identifier. As a result, the attacker could passively receive sensitive events related to that organization, such as sandbox, snapshot, volume, and runner data.

The root cause was that during the JWT handshake, the gateway joined a client-provided organization ID to a notification room without verifying if the user was actually a member of that organization. Exploitation required only a valid account and knowledge of the target organization's UUID, with no need for elevated privileges.

This vulnerability was fixed in Daytona version 0.185.0.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can lead to unauthorized disclosure of sensitive information across organizational boundaries. An attacker with a valid account could passively receive real-time notifications and events from another organization, potentially exposing confidential data such as sandbox environments, snapshots, volumes, and runner information.

Such unauthorized access can compromise the confidentiality of your organization's data and may lead to privacy breaches or competitive disadvantages.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability involves unauthorized subscription to another organization's real-time notification channel via the notification WebSocket gateway by supplying an unverified organization identifier.

Detection would involve monitoring WebSocket connections to the Daytona API service and inspecting the organization identifiers used during the JWT handshake to verify if users are subscribing only to their own organization's channels.

Since exploitation requires a valid account and knowledge of the target organization's UUID, commands or scripts could be used to log and analyze WebSocket handshake requests for mismatched or suspicious organization IDs.

Specific commands are not provided in the available resources.

Useful 0 Not Useful 0

Mitigation Strategies

The primary mitigation step is to upgrade Daytona to version 0.185.0 or later, where the vulnerability has been fixed.

Until the upgrade is applied, restrict access to the notification WebSocket gateway to trusted users and monitor for unusual subscription activity involving organization identifiers.

Note that the API-key authentication path is unaffected, so consider using API-key based authentication where possible as a temporary measure.

Useful 0 Not Useful 0