CVE-2026-123835 In JetBrains Datalore before 2026.4 code execution was possible in another user's computation via an init script upload race condition
Medium 5.9
Published
Updated
Check this codebase for CVE-2026-123835 and fix it if it is affected.
What it is: CVE-2026-123835 is a medium-severity vulnerability in JetBrains Datalore, published on 6 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-123835 in the wild and no public exploit code.
Affected product: JetBrains Datalore. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-123835/ (Markdown: https://insights.sbomify.com/CVE-2026-123835/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-123835?
CVE-2026-123835 is a medium-severity vulnerability in JetBrains Datalore, published on 6 Nov 2026.
Official description
In JetBrains Datalore before 2026.4 code execution was possible in another user's computation via an init script upload race condition
Weakness: CWE-367
Which versions are affected by CVE-2026-123835?
It affects 1 product.
Products include JetBrains Datalore.
How do I fix CVE-2026-123835?
No fix has been published for CVE-2026-123835 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-123835 being exploited?
There is no known exploitation of CVE-2026-123835 in the wild and no public exploit code.
Other vulnerabilities in JetBrains Datalore
- CVE-2026-123836 In JetBrains Datalore before 2026.4 workspace collaborators could obtain the owner's SSH private key via Git backup
- CVE-2026-123834 In JetBrains Datalore before 2026.4 improper scope validation in database tasks allowed using another workspace's service account
- CVE-2026-123285 In JetBrains Datalore before 2026.3 command execution was possible in the database task container via JVM options injection
- CVE-2026-32745 In JetBrains Datalore before 2026.1 session hijacking was possible due to missing secure attribute for cookie settings
- CVE-2026-123286 In JetBrains Datalore before 2026.4 improper authorisation allowed read the notebook owner's file storage session token
Sources
Also known as GHSA-4xrh-853p-mr3w.