NetSight

Security Dashboard

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

Reset
280 matching advisories · page 5 of 10Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.7 CVE-2026-100268 In JetBrains YouTrack before 2026.2.19197 project administrators could read comments from other projects via notification templates jetbrains · youtrack 52 days ago high7.7 CVE-2026-100266 In JetBrains Hub before 2026.2.52366 missing authorisation allowed authenticated users to send arbitrary emails from the server's trusted address jetbrains · hub 52 days ago high7.6 CVE-2026-100262 In JetBrains YouTrack before 2026.2.18991 missing authorisation allowed users with read-only project access to overwrite project notification templates jetbrains · youtrack 52 days ago high7.8 CVE-2026-100256 In JetBrains IntelliJ IDEA before 2026.2.3 rCE via Structural Search script constraints was possible in untrusted projects jetbrains · intellij_idea 52 days ago high8.1 CVE-2026-100255 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 administrator account takeover was possible via password reset jetbrains · teamcity 52 days ago high8.8 CVE-2026-100254 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 authenticated users could execute commands on Windows servers via CRLF injection in Pipeline Git conne… jetbrains · teamcity 52 days ago high8.8 CVE-2026-100253 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 sandbox escape leading to code execution was possible via the versioned settings Kotlin DSL jetbrains · teamcity 52 days ago high7.8 CVE-2026-86504 In JetBrains IntelliJ IDEA before 2026.2.2 missing project-trust confirmation before building a Dev Container allowed host-level code execution jetbrains · intellij_idea 2026-09-07 high8.4 CVE-2026-86502 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 jetbrains · intellij_idea 2026-09-07 high7.7 CVE-2026-86498 In JetBrains YouTrack before 2025.3.160480, 2026.1.14047 pUT requests on link sub-resources allowed modification linked entities without update permission JetBrains YouTrack 2026-09-07 high7.7 CVE-2026-86494 In JetBrains YouTrack before 2026.2.18634 cloning a whiteboard allowed unauthorized changes to links on inaccessible issues JetBrains YouTrack 2026-09-07 high8.5 CVE-2026-86492 In JetBrains YouTrack before 2026.2.18634 a shared token cache allowed cross-tenant theft of GitHub App installation tokens JetBrains YouTrack 2026-09-07 high8.8 CVE-2026-86482 In JetBrains YouTrack before 2026.2.18634, insufficient validation of role assignments allowed privilege escalation JetBrains YouTrack 2026-09-07 high8.1 CVE-2026-86479 In JetBrains YouTrack before 2026.2.18788, 2026.1.14055, 2025.3.161254 missing authorisation allowed access to restricted REST API resources via IDOR JetBrains YouTrack 2026-09-07 high8.4 CVE-2026-75060 In JetBrains PyCharm before 2026.2.1 code execution was possible via unauthenticated Jupyter MCP tools jetbrains · pycharm 2026-08-17 high7.8 CVE-2026-75056 In JetBrains IntelliJ IDEA before 2026.2.1 rCE via Markdown export tool was possible jetbrains · intellij_idea 2026-08-17 high8.1 CVE-2026-75051 In JetBrains YouTrack before 2026.2.17917 unauthorised project transfer between organisations was possible jetbrains · youtrack 2026-08-17 high7.1 CVE-2026-75050 In JetBrains YouTrack before 2026.1.13901, 2026.2.17950 doS attack was possible via crafted type parameters jetbrains · youtrack 2026-08-17 high8.2 CVE-2026-75048 In JetBrains YouTrack before 2026.2.18068 stored XSS via the fenced code-block language label was possible jetbrains · youtrack 2026-08-17 high8.1 CVE-2026-75044 In JetBrains YouTrack before 2025.3.156085, 2026.1.13914, 2026.2.18095 missing authorisation allowed an authenticated user to delete arbitrary entities via the… jetbrains · youtrack 2026-08-17 high8.6 CVE-2026-65908 In JetBrains PyCharm before 2026.1.4, 2026.2 arbitrary code execution via malicious Python executable was possible on untrusted project open jetbrains · pycharm 2026-07-23 high8.8 CVE-2026-65906 In JetBrains TeamCity before 2026.1.2, 2025.11.6 сode execution via Kotlin DSL sandbox escape was possible jetbrains · teamcity 2026-07-23 high8.1 CVE-2026-64815 In JetBrains IntelliJ IDEA before 2026.2 arbitrary code injection was possible via UI Designer form files jetbrains · intellij_idea 2026-07-23 high8.6 CVE-2026-64814 In JetBrains IntelliJ IDEA before 2026.2 unauthorized file access was possible in a Remote Development session jetbrains · intellij_idea 2026-07-23 high7.8 CVE-2026-64811 In JetBrains IntelliJ IDEA before 2026.2 arbitrary code execution was possible before granting project trust via development container configuration jetbrains · intellij_idea 2026-07-23 high8.4 CVE-2026-64809 In JetBrains PhpStorm before 2026.2 arbitrary code execution was possible before granting project trust via the configured interpreter jetbrains · phpstorm 2026-07-23 high8.4 CVE-2026-64808 In JetBrains PhpStorm before 2026.2 arbitrary code execution was possible before granting project trust via project tooling jetbrains · phpstorm 2026-07-23 high7.8 CVE-2026-64807 In JetBrains WebStorm before 2026.2 arbitrary code execution was possible via a project-supplied linter configuration jetbrains · webstorm 2026-07-23 high8.4 CVE-2026-64806 In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via the configured Node.js interpreter jetbrains · webstorm 2026-07-23 high8.4 CVE-2026-64805 In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via project-local package-manager tooling jetbrains · webstorm 2026-07-23

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.