Description

In JetBrains Datalore before 2026.4 improper scope validation in database tasks allowed using another workspace's service account

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.5",
  "pubDate": "2026-11-06T17:17:21.680Z",
  "pubdate": "2026-11-06T17:17:21.680Z",
  "executiveSummary": "This vulnerability, identified in JetBrains Datalore prior to version 2026.4, involves a critical flaw in authorization logic concerning database tasks. Specifically, the application suffers from improper scope validation, which permits authenticated users to leverage the service account credentials or permissions belonging to a different workspace.\nThe vulnerability type is classified as an authorization bypass or broken access control. The impact is significant, as it enables cross-workspace privilege escalation, potentially allowing unauthorized access to databases or sensitive data stores linked to another user's or team's workspace environment.\nThe vulnerability affects Datalore installations below version 2026.4. Exploitation does not require external network access if the attacker is already an authenticated user within the multi-tenant Datalore environment. By manipulating database task parameters, an attacker can coerce the application into executing queries under the security context of a foreign service account. This poses a severe risk to data confidentiality and integrity, as service accounts typically hold elevated privileges within cloud or internal database infrastructures. No complex exploitation requirements are noted beyond the ability to trigger database tasks within the application's user interface.",
  "technicalDetails": "The root cause of this vulnerability lies in the insufficient enforcement of workspace-level isolation boundaries within the database task execution engine. In JetBrains Datalore, database tasks are intended to operate within the context of the user's specific workspace, utilizing scoped credentials or service accounts tied strictly to that workspace's configuration.\nThe vulnerability exists because the backend service responsible for managing database task requests fails to adequately validate that the requester's identity or current workspace ID matches the owner of the service account requested for the task execution. Consequently, the application processes the database task without verifying if the requested service account resource belongs to the current workspace's authorized scope.\nThe exploitation method involves an attacker crafting a request to the database task execution endpoint. By modifying the target workspace or service account identifier within the task configuration metadata, the attacker can hijack a service account associated with a different, often higher-privileged, workspace. When the Datalore backend receives this request, it performs a lookup and, due to the missing scope validation check, proceeds to initialize the database connection using the foreign service account credentials.\nThe attack flow follows these steps: 1) The attacker identifies a target workspace or service account identifier via observation or predictable resource patterns. 2) The attacker initiates a new database task within their own authorized workspace. 3) The attacker intercepts or modifies the task request parameters to reference the resource identifier of the target workspace. 4) The backend service processes the request, fails to check if the user has permissions for the target resource, and executes the database operation using the elevated privileges of the target service account. 5) The attacker receives the results of the database query, effectively bypassing the intended sandbox.\nThis vulnerability enables an attacker to perform unauthorized data extraction, manipulation, or administrative actions on databases that should be inaccessible to them. Because the actions are performed by the target's legitimate service account, the logs may reflect the activity as authorized behavior, complicating incident response and audit processes. The flaw indicates a failure in the application's resource authorization controller which is responsible for enforcing multi-tenant isolation."
}