In JetBrains Datalore before 2026.4 improper scope validation in database tasks allowed using another workspace's service account
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.4
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2026.4.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
JetBrains Datalore, a data science platform, is affected by a flaw where database tasks do not properly check scope, letting a user run them with another workspace's service account. An attacker with low-privilege login can exploit this remotely over the network, with no user action required.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
In JetBrains Datalore before 2026.4 improper scope validation in database tasks allowed using another workspace's service account
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 7.5, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2026.4.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- JetBrains Datalore
fixed in 2026.4
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123834
Is CVE-2026-123834 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-123834?
Datalore: before 2026.4.Source: cve.now feed data
How do I fix CVE-2026-123834?
Upgrade to a fixed version: 2026.4.Source: cve.now feed data