Improper link resolution in JetBrains Datalore exposes SSH private keys
In JetBrains Datalore before 2026.4 workspace collaborators could obtain the owner's SSH private key via Git backup
15 records
In JetBrains Datalore before 2026.4 workspace collaborators could obtain the owner's SSH private key via Git backup
In JetBrains Datalore before 2026.4 code execution was possible in another user's computation via an init script upload race condition
In JetBrains Datalore before 2026.4 improper scope validation in database tasks allowed using another workspace's service account
In JetBrains Datalore before 2026.4 aPI tokens and sessions of removed or banned users remained valid
In JetBrains Datalore before 2026.4 improper owner validation allowed reading another workspace's issues and runs notebook
In JetBrains Datalore before 2026.4 hidden notebook code was exposed to unauthenticated users via the public interactive report content endpoint
In JetBrains Datalore before 2026.4 improper authorisation allowed notebook viewers to modify files
In JetBrains Datalore before 2026.4 stored XSS in notebook charts was possible via Vega editor link
In JetBrains Datalore before 2026.4 private notebook files could be downloaded without authentication via published interactive reports
In JetBrains Datalore before 2026.4 improper authorisation allowed read the notebook owner's file storage session token
In JetBrains Datalore before 2026.4 improper authorisation on workspace moves allowed view-only collaborators to modify shared content
In JetBrains Datalore before 2026.4 account takeover was possible via SSO sign-in to a pre-registered account
In JetBrains Datalore before 2026.4 missing expiration validation of account tokens allowed a new authenticated session
In JetBrains Datalore before 2026.4 notebook code could execute commands in the sidecar container via the mount broker
In JetBrains Datalore before 2026.4 code execution was possible in a notebook's computation by view-only collaborators