NetSight

Security Dashboard

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

Reset
66 matching advisories · page 1 of 3Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2026-132891 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via external pull requests JetBrains · TeamCity 3 days ago critical10.0 CVE-2026-75521 Miren Runtime: Authentication bypass in RPC layer: unverified TLS client certificates grant cluster superuser access go · miren.dev/runtime 3 days ago critical9.9 CVE-2026-132234 In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Mercurial VCS root settings JetBrains · TeamCity 3 days ago critical9.9 CVE-2026-132233 In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via build attribute injection JetBrains · TeamCity 3 days ago critical9.9 CVE-2026-132232 In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Perforce settings JetBrains · TeamCity 3 days ago critical9.9 CVE-2026-132231 In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via best-fit character mapping in Perforce settings JetBrains · TeamCity 3 days ago critical9.6 CVE-2026-123832 In JetBrains CLion before 2026.2 code execution was possible in Safe Mode via JSON compilation database JetBrains · CLion 15 days ago critical9.6 CVE-2026-123831 In JetBrains CLion before 2026.2, 2026.1.4 code execution was possible in Safe Mode via Meson project settings JetBrains · CLion 15 days ago critical9.6 CVE-2026-123294 In JetBrains Hub before 2026.2.52556 privilege escalation was possible by changing email authentication details during the verification flow JetBrains · Hub 16 days ago critical9.0 CVE-2026-123279 In JetBrains Datalore before 2026.4 code execution was possible in a notebook's computation by view-only collaborators JetBrains · Datalore, jetbrains · datalore 16 days ago critical9.0 CVE-2026-118697 In JetBrains Toolbox App before 3.9.1 and 3.8.2; IntelliJ IDEA, PyCharm, PhpStorm, RubyMine, WebStorm, GoLand and Rider before 2026.3 and 2026.2.4; CLion befor… JetBrains · Toolbox App, JetBrains · IntelliJ IDEA, JetBrains · PyCharm +8 22 days ago critical9.8 CVE-2026-108474 In JetBrains Exposed before 1.5.1 sQL injection was possible via unescaped string arguments of several SQL functions JetBrains Exposed 43 days ago critical9.8 CVE-2026-86480 In JetBrains Hub before 2026.2.52442 an unauthenticated attacker could register a trusted service and gain superuser privileges JetBrains Hub 2026-09-07 critical9.8 CVE-2026-86478 In JetBrains YouTrack before 2025.3.161254, 2026.1.14042 improper authentication in YouTrack Helpdesk allowed unauthenticated account takeover via a self-asser… JetBrains YouTrack 2026-09-07 critical9.1 CVE-2026-75045 In JetBrains YouTrack before 2025.3.156085, 2026.1.13913, 2026.2.18112 an unauthenticated attacker could download database backups via shared draft signature jetbrains · youtrack 2026-08-17 critical9.8 CVE-2026-63077 JetBrains TeamCity Deserialization of Untrusted Data VulnerabilityExploited JetBrains · TeamCity, jetbrains · teamcity 2026-07-27 critical9.1 CVE-2026-65907 In JetBrains TeamCity before 2026.1.2, 2025.11.6 code execution in Git VCS roots was possible JetBrains TeamCity 2026-07-23 critical10.0 CVE-2026-64813 In JetBrains IntelliJ IDEA before 2026.2 unauthorized settings modification was possible in a Remote Development session jetbrains · intellij_idea 2026-07-23 critical10.0 CVE-2026-64812 In JetBrains IntelliJ IDEA before 2026.2 unauthorized input injection was possible in a Remote Development session jetbrains · intellij_idea 2026-07-23 critical10.0 CVE-2026-62422 In JetBrains YouTrack before 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429 authentication bypass via direct database … jetbrains · youtrack 2026-07-14 critical9.6 CVE-2026-59792 In JetBrains IntelliJ IDEA before 2026.1.4, 2026.2 code execution via path traversal in project workspace ID handling was possible jetbrains · intellij_idea 2026-07-10 critical9.9 CVE-2026-56142 In JetBrains Hub before 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429 privilege escalation by attaching authenticatio… jetbrains · hub 2026-06-19 critical9.8 CVE-2026-56141 In JetBrains Hub before 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429 account takeover via predictable restore codes … jetbrains · hub 2026-06-19 critical10.0 CVE-2026-50242 In JetBrains Hub before 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429 authentication bypass via direct database acces… jetbrains · hub 2026-06-19 critical9.1 CVE-2026-25848 In JetBrains Hub before 2025.3.119807 authentication bypass allowing administrative actions was possible jetbrains · hub 2026-02-09 critical9.3 CVE-2024-37051 GitHub access token could be exposed to third-party sites in JetBrains IDEs after version 2023.1 and less than: IntelliJ IDEA 2023.1.7, 2023.2.7, 2023.3.7, 202… jetbrains · aqua, jetbrains · clion, jetbrains · datagrip +22 2024-06-10 critical9.8 CVE-2024-27198 JetBrains TeamCity Authentication Bypass VulnerabilityExploited jetbrains · teamcity 2024-03-04 critical9.8 CVE-2024-23917 In JetBrains TeamCity before 2023.11.3 authentication bypass leading to RCE was possible jetbrains · teamcity 2024-02-06 critical9.8 CVE-2023-42793 JetBrains TeamCity Authentication Bypass VulnerabilityExploited jetbrains · teamcity 2023-09-19 critical9.1 CVE-2023-34218 In JetBrains TeamCity before 2023.05 bypass of permission checks allowing to perform admin actions was possible jetbrains · teamcity 2023-05-31

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.