CVE-2026-123285: In JetBrains Datalore before 2026.3 command execution was possible in the database task container via JVM options injection
Noroxi assessment
Priority: Monitor (action score 25/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.85% (FIRST EPSS); higher than 58.6% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: JetBrains Datalore 2026.3.
Low priority for now. Upgrade to JetBrains Datalore 2026.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- Published
- Nov 6, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.8% · 58th percentile
- CWE
- CWE-88
Report tools
Action score
25
Low priority for now.
- CVSS
- 25 / 40 · 6.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · JetBrains
- 6.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (JetBrains). Independent of NVD's CPE analysis and usually ahead of it.
JetBrains Datalore
- before 2026.3affected · semver
Same product
jetbrains: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-123279In JetBrains Datalore before 2026.4 code execution was possible in a notebook's computation by view-only collaborators36Monitor
- CVE-2026-123836In JetBrains Datalore before 2026.4 workspace collaborators could obtain the owner's SSH private key via Git backup35Monitor
- CVE-2026-123280In JetBrains Datalore before 2026.2.4 unauthenticated users could execute code via published interactive reports32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-123283Nov 6, 2026 · In JetBrains Datalore before 2026.4 account takeover was possible via SSO sign-in to a pre-registered account27Monitor
- ← EarlierCVE-2026-123284Nov 6, 2026 · In JetBrains Datalore before 2026.4 improper authorisation on workspace moves allowed view-only collaborators to modify shared content26Monitor
- Later →CVE-2026-123286Nov 6, 2026 · In JetBrains Datalore before 2026.4 improper authorisation allowed read the notebook owner's file storage session token23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| JetBrains Datalore | 2026.3 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 12, 2026+6 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1232810 days apartIn JetBrains Datalore before 2026.4 notebook code could execute commands in the sidecar container via the mount broker30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-1232870 days apartIn JetBrains Datalore before 2026.4 private notebook files could be downloaded without authentication via published interactive reports23Monitor
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-88 · Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Parameter InjectionCAPEC-137likelihood: Medium · Medium
- Flash Parameter InjectionCAPEC-174likelihood: High · Medium
- Using Meta-characters in E-mail Headers to Inject Malicious PayloadsCAPEC-41likelihood: High · High
- HTTP Parameter Pollution (HPP)CAPEC-460Medium
- OS Command InjectionCAPEC-88likelihood: High · High
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.