Latest CVE Feed
Vulnerabilities published in the last 30 days. Filter by severity, exploit status, or attack vector.
In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 stored XSS was possible on the built-in web server via Markdown preview
In JetBrains IntelliJ IDEA before 2026.3 code execution via the document import was possible in untrusted projects
In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 unauthenticated connection to an arbitrary host via run configurations was possible
In JetBrains IntelliJ IDEA before 2026.3 improper checks allowed server certificates to be added to the trust store during headless runs
In JetBrains IntelliJ IDEA before 2026.3 path traversal was possible via unpacking Dev Container archives from a remote host
In JetBrains IntelliJ IDEA before 2026.3 code execution in untrusted projects via a configured ShellCheck path
In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4, 2026.1.5.1, 2025.3.6.2 code execution was possible in untrusted projects via script engine discovery
In JetBrains IntelliJ IDEA before 2026.3 dOM-based XSS in the OpenAPI preview error view was possible
In JetBrains Hub before 2026.2.52519 missing authorisation allowed users with read-only access to modify auth module group mappings
In JetBrains Hub before 2026.2.52519 information disclosure via user search queries was possible
In JetBrains Hub before 2026.2.52556 sMTP command injection via email verification was possible
In JetBrains Hub before 2026.2.52519 two-factor authentication bypass was possible via the password reset flow
In JetBrains Hub before 2026.2.52519 privilege escalation via forged email verification was possible
In JetBrains Hub before 2026.2.52519 enforced two-factor authentication could be disabled via the profile update endpoint
In JetBrains Hub before 2026.2.52556 privilege escalation was possible by changing email authentication details during the verification flow
In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 code execution was possible in untrusted projects via the Terraform tool path setting
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