Skip to content
OpenAdvisories

Archive

6 November 2026

Vulnerabilities first published on this day (UTC), newest first.

  1. 1102
  2. 2473
  3. 3780
  4. 4395
  5. 5456
  6. 6465
  7. 7474
  8. 8323
  9. 9525
  10. 102065
  11. 11692
  12. 12388
  13. 13771
  14. 1465
  15. 15111
  16. 1612
  17. 17 
  18. 18 
  19. 19 
  20. 20 
  21. 21 
  22. 22 
  23. 23 
  24. 24 
  25. 25 
  26. 26 
  27. 27 
  28. 28 
  29. 29 
  30. 30 

465 results · Feed

  • Medium 5.5

    In JetBrains Junie CLI before 26.6.29 sensitive environment variables were exposed in session event logs

  • High 8.1

    In JetBrains Ktor before 3.6.1 session forgery was possible via tampered encrypted session cookies

  • Medium 4.8

    In JetBrains Ktor before 3.6.1 hTTP request smuggling was possible in the CIO engine

  • Low 3.1

    In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 xXE attack was possible via an XML response to an HTTP Client request

  • High 7.0

    In JetBrains Junie CLI before 26.8.24 command execution was possible via the Allow Similar Commands option

  • Medium 5.3

    In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 command execution via a hidden run control in the Markdown preview w…

  • Low 3.3

    In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 sSRF was possible via annotations.xml files during indexing

  • Low 3.3

    In JetBrains IntelliJ IDEA before 2026.3 improper checks could enable disabled plugins via external dependency settings

  • Medium 6.1

    In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 stored XSS was possible on the built-in web server via Markdown prev…

  • Medium 5.4

    In JetBrains IntelliJ IDEA before 2026.3 kotlin scripts could trigger dependency downloads from arbitrary repositories …

  • Medium 6.8

    In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 unauthenticated connection to an arbitrary host via run configuratio…

  • Medium 6.3

    In JetBrains IntelliJ IDEA before 2026.3 code execution via the document import was possible in untrusted projects

  • High 7.8

    In JetBrains IntelliJ IDEA before 2026.3 code execution in untrusted projects via a configured ShellCheck path

  • High 7.5

    In JetBrains IntelliJ IDEA before 2026.3 path traversal was possible via unpacking Dev Container archives from a remote…

  • High 7.4

    In JetBrains IntelliJ IDEA before 2026.3 improper checks allowed server certificates to be added to the trust store dur…

  • High 8.2

    In JetBrains IntelliJ IDEA before 2026.3 dOM-based XSS in the OpenAPI preview error view was possible

  • High 7.8

    In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4, 2026.1.5.1, 2025.3.6.2 code execution was possible in untrusted pro…

  • Low 3.1

    In JetBrains Hub before 2026.2.52519 information disclosure via user search queries was possible

  • Low 2.7

    In JetBrains Hub before 2026.2.52519 missing authorisation allowed users with read-only access to modify auth module gr…

  • Medium 6.8

    In JetBrains Hub before 2026.2.52519 two-factor authentication bypass was possible via the password reset flow

  • Medium 5.0

    In JetBrains Hub before 2026.2.52556 sMTP command injection via email verification was possible

  • High 8.1

    In JetBrains Hub before 2026.2.52519 enforced two-factor authentication could be disabled via the profile update endpoi…

  • High 7.5

    In JetBrains Hub before 2026.2.52519 privilege escalation via forged email verification was possible

  • Low 2.7

    In JetBrains Datalore before 2026.4 aPI tokens and sessions of removed or banned users remained valid

  • High 7.8

    In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 code execution was possible in untrusted projects via the Terraform …

  • Critical 9.6

    In JetBrains Hub before 2026.2.52556 privilege escalation was possible by changing email authentication details during …

  • Medium 5.3

    In JetBrains Datalore before 2026.4 hidden notebook code was exposed to unauthenticated users via the public interactiv…

  • Medium 4.3

    In JetBrains Datalore before 2026.4 improper owner validation allowed reading another workspace's issues and runs noteb…

  • Medium 5.4

    In JetBrains Datalore before 2026.4 stored XSS in notebook charts was possible via Vega editor link

  • Medium 5.4

    In JetBrains Datalore before 2026.4 improper authorisation allowed notebook viewers to modify files

  • Medium 5.9

    In JetBrains Datalore before 2026.4 improper authorisation allowed read the notebook owner's file storage session token

  • Medium 5.9

    In JetBrains Datalore before 2026.4 private notebook files could be downloaded without authentication via published int…

  • Medium 6.5

    In JetBrains Datalore before 2026.4 improper authorisation on workspace moves allowed view-only collaborators to modify…

  • Medium 6.3

    In JetBrains Datalore before 2026.3 command execution was possible in the database task container via JVM options injec…

  • High 7.4

    In JetBrains Datalore before 2026.4 missing expiration validation of account tokens allowed a new authenticated session

  • Medium 6.8

    In JetBrains Datalore before 2026.4 account takeover was possible via SSO sign-in to a pre-registered account

  • High 8.1

    In JetBrains Datalore before 2026.2.4 unauthenticated users could execute code via published interactive reports

  • High 7.5

    In JetBrains Datalore before 2026.4 notebook code could execute commands in the sidecar container via the mount broker

  • Medium 6.7

    In JetBrains IntelliJ IDEA before 2026.3 code execution was possible via the unauthenticated JDBC worker RMI endpoint

  • Critical 9.0

    In JetBrains Datalore before 2026.4 code execution was possible in a notebook's computation by view-only collaborators