Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-111093 Overview
CVE-2026-111093 is an unauthenticated path traversal vulnerability in JetBrains Datalore versions before 2026.2.1. The flaw resides in the report blob endpoint, which fails to properly validate user-supplied path components. Attackers can traverse directory structures and read arbitrary files on the host system without authentication. The weakness is categorized under CWE-23 (Relative Path Traversal). Because the endpoint requires no credentials and the attack originates over the network, exploitation requires only the ability to reach the Datalore web service.
Critical Impact
Unauthenticated remote attackers can read arbitrary files from the Datalore server, exposing configuration data, secrets, source code, and notebook contents.
Affected Products
- JetBrains Datalore versions prior to 2026.2.1
- Self-hosted Datalore deployments exposing the report blob endpoint
- Any Datalore instance reachable over the network without upstream access controls
Discovery Timeline
- 2026-10-15 - CVE-2026-111093 published to NVD
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-111093
Vulnerability Analysis
The vulnerability resides in the report blob endpoint of JetBrains Datalore. The endpoint accepts a file or blob identifier that is incorporated into a filesystem path without adequate normalization. An attacker who supplies traversal sequences such as ../ can escape the intended blob directory. The endpoint does not require authentication, so any network-reachable client can issue the request. Successful exploitation yields read access to files that the Datalore service account can access on the host.
Typical targets include application configuration files, database credentials, TLS private keys, and system files such as /etc/passwd. Attackers can also retrieve notebook content, user workspace data, and internal service tokens. Harvested secrets often enable lateral movement into connected databases, object storage, and single sign-on systems.
Root Cause
The root cause is insufficient sanitization of path components in the report blob handler. The handler concatenates attacker-controlled input into a filesystem path without canonicalizing the resulting path and verifying it stays within the blob storage directory. [CWE-23] describes this pattern precisely: relative path sequences are preserved through the resolution logic.
Attack Vector
Exploitation is performed by sending an HTTP request to the vulnerable report blob endpoint with a crafted blob identifier containing traversal sequences. No credentials, user interaction, or elevated privileges are required. The attack targets confidentiality only; the endpoint does not permit writing or executing files through this flaw. Refer to the JetBrains Security Issues Fixes advisory for vendor-published details.
Detection Methods for CVE-2026-111093
Indicators of Compromise
- HTTP requests to the Datalore report blob endpoint containing ../, ..%2f, ..%5c, or double-encoded traversal sequences in the path or query string.
- Access log entries where the blob identifier parameter references absolute paths or sensitive filenames such as passwd, shadow, .env, or application configuration files.
- Unusual spikes in 200-status responses from the report blob endpoint originating from a single source IP.
- Datalore service account reading files outside its normal blob storage directory.
Detection Strategies
- Deploy web application firewall rules that reject requests to Datalore endpoints containing encoded or raw path traversal sequences.
- Enable verbose HTTP access logging on the Datalore reverse proxy and alert on blob endpoint anomalies.
- Correlate process-level file reads by the Datalore service with its expected working directories using endpoint telemetry.
Monitoring Recommendations
- Forward Datalore and reverse-proxy logs to a central analytics platform for retention and pattern analysis.
- Baseline normal request paths for the report blob endpoint and alert on deviations.
- Monitor outbound connections from the Datalore host for signs of secret-driven lateral movement after suspicious reads.
How to Mitigate CVE-2026-111093
Immediate Actions Required
- Upgrade all JetBrains Datalore instances to version 2026.2.1 or later without delay.
- Restrict network access to the Datalore web interface to trusted networks or VPN clients until patching is complete.
- Rotate any credentials, API tokens, or TLS keys stored on affected Datalore hosts, since file reads may have exposed them.
- Review access logs for traversal patterns dating back to the earliest log retention window.
Patch Information
JetBrains has addressed CVE-2026-111093 in JetBrains Datalore 2026.2.1. Administrators should consult the JetBrains Security Issues Fixes page for release notes and upgrade instructions. Apply the update through the standard Datalore upgrade workflow and verify the installed version after the upgrade.
Workarounds
- Place Datalore behind a reverse proxy that blocks requests containing path traversal sequences targeting the report blob endpoint.
- Enforce IP allow-listing or authenticated VPN access to the Datalore service until the patched version is deployed.
- Run the Datalore service under a low-privilege account whose filesystem access is confined to required directories.
# Example NGINX reverse-proxy rule to block traversal attempts
location ~* /report.*blob {
if ($request_uri ~* "(\.\./|\.\.%2f|\.\.%5c|%2e%2e)") {
return 403;
}
proxy_pass http://datalore_backend;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

