NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
280 matching advisories · page 4 of 10Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.1 CVE-2026-123326 In JetBrains YouTrack before 2026.2.19197 incorrect authorisation in the scripts debugger allowed workflow script disclosure and suspension JetBrains YouTrack 16 days ago high7.7 CVE-2026-123324 In JetBrains YouTrack before 2026.2.19562 information disclosure via shared mailbox message history was possible JetBrains YouTrack 16 days ago high7.1 CVE-2026-123325 In JetBrains YouTrack before 2025.3.170763, 2026.1.14150, 2026.2.19656 inclusion of untrusted remote code was possible via the plugin sandbox page JetBrains · YouTrack 16 days ago high7.8 CVE-2026-123321 In JetBrains WebStorm before 2026.3, 2026.2.3 code execution via Grunt and Gulp task loading was possible in untrusted projects JetBrains · WebStorm 16 days ago high8.4 CVE-2026-123323 In JetBrains YouTrack before 2025.3.170763, 2026.1.14150, 2026.2.19656 improper URL validation in the app widget host allowed apps to send REST requests withou… JetBrains · YouTrack 16 days ago high8.1 CVE-2026-123317 In JetBrains Ktor before 3.6.1 session forgery was possible via tampered encrypted session cookies JetBrains · Ktor 16 days ago high7.0 CVE-2026-123315 In JetBrains Junie CLI before 26.8.24 command execution was possible via the Allow Similar Commands option JetBrains · Junie CLI 16 days ago high7.8 CVE-2026-123304 In JetBrains IntelliJ IDEA before 2026.3 code execution in untrusted projects via a configured ShellCheck path JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 16 days ago high7.5 CVE-2026-123305 In JetBrains IntelliJ IDEA before 2026.3 path traversal was possible via unpacking Dev Container archives from a remote host JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 16 days ago high7.4 CVE-2026-123306 In JetBrains IntelliJ IDEA before 2026.3 improper checks allowed server certificates to be added to the trust store during headless runs JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 16 days ago high8.2 CVE-2026-123301 In JetBrains IntelliJ IDEA before 2026.3 dOM-based XSS in the OpenAPI preview error view was possible JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 16 days ago high7.8 CVE-2026-123302 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 JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 16 days ago high7.5 CVE-2026-123296 In JetBrains Hub before 2026.2.52519 privilege escalation via forged email verification was possible JetBrains · Hub 16 days ago high8.1 CVE-2026-123295 In JetBrains Hub before 2026.2.52519 enforced two-factor authentication could be disabled via the profile update endpoint JetBrains · Hub 16 days ago high7.8 CVE-2026-123293 In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 code execution was possible in untrusted projects via the Terraform tool path setting JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 16 days ago high7.4 CVE-2026-123282 In JetBrains Datalore before 2026.4 missing expiration validation of account tokens allowed a new authenticated session JetBrains · Datalore, jetbrains · datalore 16 days ago high8.1 CVE-2026-123280 In JetBrains Datalore before 2026.2.4 unauthenticated users could execute code via published interactive reports JetBrains · Datalore, jetbrains · datalore 16 days ago high7.5 CVE-2026-123281 In JetBrains Datalore before 2026.4 notebook code could execute commands in the sidecar container via the mount broker JetBrains · Datalore, jetbrains · datalore 16 days ago high7.8 CVE-2026-123276 In JetBrains CLion before 2026.3, 2026.2.4.1 code execution was possible in Safe Mode via a crafted GDB server debug profile JetBrains · CLion 16 days ago high8.0 CVE-2026-118696 In JetBrains IntelliJ IDEA, PyCharm, PhpStorm, RubyMine and WebStorm before 2026.3, 2026.2.4, 2026.1.5.1, and 2025.3.6.2; GoLand before 2026.3, 2026.2.4, 2026.… 2026.2.4, 2026.1.5.1, and 2025.3.6.2; GoLand, 2026.2.4, 2026.1.5.1, and 2025.3.5.2; Rider, 2026.2.4, 2026.1.5.3, and 2025.3.5.3; CLion +3 22 days ago high8.0 CVE-2026-111095 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the classic project overview was possible jetbrains · teamcity 37 days ago high8.1 CVE-2026-111094 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution via a whitelist bypass in the build messages protocol was possible jetbrains · teamcity 37 days ago high7.5 CVE-2026-111093 In JetBrains Datalore before 2026.2.1 unauthenticated path traversal via the report blob endpoint allowed reading arbitrary files jetbrains · datalore 37 days ago high7.8 CVE-2026-111091 In JetBrains Junie CLI before 26.8.3 code execution was possible via an untrusted project's MCP server configuration JetBrains Junie CLI 37 days ago high8.8 CVE-2026-106218 In JetBrains TeamCity before 2026.1.3 2025.11.7 kotlin DSL sandbox escape leading to RCE on the server was possible jetbrains · teamcity 46 days ago high8.1 CVE-2026-103493 In JetBrains YouTrack before 2026.2.19422 stored XSS via Mermaid and LaTeX content was possible jetbrains · youtrack 52 days ago high7.2 CVE-2026-103490 In JetBrains YouTrack before 2026.2.19422 privilege escalation was possible via user group links jetbrains · youtrack 52 days ago high7.1 CVE-2026-103488 In JetBrains YouTrack before 2026.2.19422 missing authorisation allowed authenticated users to add themselves to project teams and access restricted issues jetbrains · youtrack 52 days ago high8.9 CVE-2026-100277 In JetBrains YouTrack before 2026.2.19197 account takeover was possible by replaying a notification signature jetbrains · youtrack 52 days ago high8.2 CVE-2026-100273 In JetBrains YouTrack before 2026.2.19197 authorisation bypass in the scripts debugger allowed arbitrary code execution jetbrains · youtrack 52 days ago

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.