JetBrains Datalore CVE-2026-111093

Exploitation requires network reachability to a JetBrains Datalore instance running a version before 2026.2.1 and the ability to send requests to the report blob endpoint; per the CVSS vector (PR:N/UI:N) no authentication or user interaction is needed, so any party able to reach the service HTTP interface can attempt it. The limiting factors are deployment exposure (the Datalore instance must be network-accessible to the attacker, e.g. internet-facing rather than restricted to an internal network) and version (instances already at 2026.2.1 or later are not affected). Impact is limited to reading files the Datalore service process can access; there is no integrity or availability impact (I:N/A:N), so this alone does not grant code execution.

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5 HIGH) describes a cleanly exploitable network-reachable, unauthenticated flaw with low complexity and no user interaction - all signals that favor easy exploitation. Impact is confined to confidentiality (C:H, I:N, A:N), consistent with an arbitrary file-read path traversal (CWE-23) rather than code execution. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no evidence of active exploitation or weaponization at this time; the current signal is 'no public exploit identified at time of analysis.' The practical risk is therefore driven by ease of exploitation against exposed instances rather than by observed in-the-wild activity, and is tempered by the product's comparatively narrow deployment footprint. Note that the only reference is a generic JetBrains security-bulletin landing page, not a CVE-specific advisory, so fix details beyond 'before 2026.2.1' could not be independently corroborated.

An attacker who can reach a Datalore instance's web interface sends a crafted request to the report blob endpoint containing directory-traversal sequences, requiring no credentials or user interaction. The server returns the contents of arbitrary files outside the intended blob directory - such as configuration files, credentials, or notebook data - enabling information disclosure. No public exploit code was identified at the time of analysis.