JVM Options Injection Enables Command Execution in JetBrains Datalore Database Tasks
In JetBrains Datalore before 2026.3 command execution was possible in the database task container via JVM options injection
In JetBrains Datalore before 2026.3 command execution was possible in the database task container via JVM options injection
In JetBrains Datalore before 2026.4 improper authorisation allowed read the notebook owner's file storage session token
In JetBrains Datalore before 2026.4 private notebook files could be downloaded without authentication via published interactive reports
In JetBrains Datalore before 2026.4 stored XSS in notebook charts was possible via Vega editor link
In JetBrains Datalore before 2026.4 improper authorisation allowed notebook viewers to modify files
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 owner validation allowed reading another workspace's issues and runs notebook
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 IntelliJ IDEA before 2026.2.2 terminal command input could be written to idea.log
In JetBrains IntelliJ IDEA before 2026.2.2 missing TLS and authentication on the IJent gRPC server allowed local code execution on Remote Development hosts
In JetBrains IntelliJ IDEA before 2026.2.2 opening an untrusted project could trigger SSRF via Kubernetes spec-source URL fetching
In JetBrains IntelliJ IDEA before 2026.2.2 missing project-trust confirmation before building a Dev Container allowed host-level code execution
In JetBrains IntelliJ IDEA before 2026.2.2 missing project-trust check leaked project metadata to JetBrains Marketplace
In JetBrains IntelliJ IDEA before 2026.3 code execution was possible in untrusted projects via the Terraform File Watchers
In JetBrains IntelliJ IDEA before 2026.3 host name verification was missing for server TLS certificates
In JetBrains IntelliJ IDEA before 2026.3 command execution was possible via control characters in terminal command completion
In JetBrains IntelliJ IDEA before 2026.3 blind SSRF was possible via remote references in JSON Schema validation