Description

In JetBrains Datalore before 2026.4 hidden notebook code was exposed to unauthenticated users via the public interactive report content endpoint

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "5.3",
  "pubDate": "2026-11-06T11:17:07.583Z",
  "pubdate": "2026-11-06T11:17:07.583Z",
  "executiveSummary": "A vulnerability exists in JetBrains Datalore prior to version 2026.4, allowing unauthenticated users to access hidden notebook code via the public interactive report content endpoint.\nThis represents an Improper Access Control vulnerability where the application fails to enforce appropriate authorization checks on sensitive notebook data.\nThe flaw allows unauthorized actors to retrieve proprietary, sensitive, or confidential code snippets stored within notebooks that were intended to be private or hidden.\nThe impact includes the potential leakage of intellectual property, API keys, credentials, or other sensitive configuration details embedded within the notebook environment.\nThe vulnerability is remotely exploitable without authentication, posing a significant risk to the confidentiality of data hosted within the Datalore platform.\nThe risk implication is high, as it grants attackers access to sensitive internal logic and potentially data processing workflows without requiring valid user credentials or elevated privileges.",
  "technicalDetails": "The root cause of the vulnerability lies in an insecure access control mechanism within the public interactive report content endpoint of JetBrains Datalore.\nSpecifically, the API responsible for rendering or fetching content for public interactive reports does not correctly validate the authorization state of the requesting user against the visibility settings of individual notebook cells or hidden code segments.\nIn a secure configuration, the endpoint should filter out any code or data explicitly marked as hidden or private before serving the response to an external entity.\nDue to a failure in the server-side logic, the endpoint incorrectly exposes the complete raw content of the notebook, including segments intended for internal use only.\nThe attack flow proceeds as follows: 1. An attacker identifies a public interactive report hosted on a Datalore instance. 2. The attacker interacts with the public endpoint responsible for serving the notebook structure and content. 3. Because the endpoint does not perform an authentication handshake or verify the user's permissions, it processes the request and returns the full JSON or object representation of the notebook. 4. The attacker parses the returned content to extract hidden or obfuscated code cells that were supposed to be protected from public view.\nThis vulnerability affects all JetBrains Datalore versions prior to 2026.4. The component responsible is the interactive report rendering service, which likely uses a shared data access layer that ignores the 'hidden' attribute when processing requests from the public-facing API.\nExploitation requires minimal technical effort, as the attacker only needs to send an HTTP GET request to the vulnerable endpoint to retrieve the unauthorized content. There are no special privilege requirements, as the vulnerability is accessible to unauthenticated users.\nPost-exploitation impact involves the unauthorized disclosure of sensitive data, which may be leveraged for further attacks, such as credential harvesting, intellectual property theft, or gaining deeper insight into internal infrastructure through leaked configuration variables and code logic."
}