JetBrains Datalore auth bypass leaks environment variables in notebooks
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.4.1
- Who is exposed
- Not reported
Summary
JetBrains Datalore has an improper authorization flaw that lets notebook viewers read the values of attached environment variables. An attacker can exploit it remotely with a low-privilege login and no action from a user.
Written by a model
Original description
In JetBrains Datalore before 2026.4.1 improper authorization allowed notebook viewers to read attached environment variable values
What to do
Upgrade to a fixed version: 2026.4.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133251 (In JetBrains Datalore before 2026.4.1 improper authorization allowed notebook viewers to read attached environment variable values), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133251 (entry last updated 2026-11-19):
Affected:
- JetBrains Datalore: fixed in 2026.4.1
Fixed versions: 2026.4.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133251 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133251 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.jetbrains.com/privacy-security/issues-fixed/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133251
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133251"}.Affected versions
- JetBrains Datalorefixed in 2026.4.1
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | jetbrains.com · privacy-security/issues-fixed |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133251 |
| Record | NVD · CVE-2026-133251 |
Questions about CVE-2026-133251
Is CVE-2026-133251 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133251?
Datalore: before 2026.4.1.
Source: cve.now feed data
How do I fix CVE-2026-133251?
Upgrade to a fixed version: 2026.4.1.
Source: cve.now feed data
Related
- CVE-2026-123279In JetBrains Datalore before 2026.4 code execution was possible in a notebook's computation by view-only collaborators
- CVE-2026-123836In JetBrains Datalore before 2026.4 workspace collaborators could obtain the owner's SSH private key via Git backup
- CVE-2026-123280In JetBrains Datalore before 2026.2.4 unauthenticated users could execute code via published interactive reports
- CVE-2026-123834In JetBrains Datalore before 2026.4 improper scope validation in database tasks allowed using another workspace's service account
- CVE-2026-123281In JetBrains Datalore before 2026.4 notebook code could execute commands in the sidecar container via the mount broker
- CVE-2026-111093In JetBrains Datalore before 2026.2.1 unauthenticated path traversal via the report blob endpoint allowed reading arbitrary files
No corrections so far. Something wrong on this page? Report an error.