NetSight

Security Dashboard

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

Reset
280 matching advisories · page 6 of 10Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.4 CVE-2026-64804 In JetBrains WebStorm before 2026.2 arbitrary code execution was possible before granting project trust via project-local linter tooling jetbrains · webstorm 2026-07-23 high7.8 CVE-2026-64803 In JetBrains GoLand before 2026.2 arbitrary code execution was possible before granting project trust via the configured Go SDK jetbrains · goland 2026-07-23 high7.8 CVE-2026-64802 In JetBrains GoLand before 2026.2 arbitrary code execution was possible before granting project trust in the Go Modules integration jetbrains · goland 2026-07-23 high7.8 CVE-2026-50510 Improper restriction of names for files and other resources in Github Copilot allows an unauthorized attacker to execute code locally. microsoft · github_copilot, Microsoft · GitHub Copilot Plugin for JetBrains IDEs 2026-07-14 high8.1 CVE-2026-59796 In JetBrains TeamCity before 2026.1.2 pipeline modification was possible due to improper permission checks jetbrains · teamcity 2026-07-10 high8.1 CVE-2026-59795 In JetBrains TeamCity before 2026.1.2 stored XSS via unauthenticated agent registration was possible jetbrains · teamcity 2026-07-10 high7.3 CVE-2026-59794 In JetBrains TeamCity before 2026.1.2 stored XSS on the cloud profile page was possible via agent-reported data jetbrains · teamcity 2026-07-10 high8.8 CVE-2026-59793 In JetBrains TeamCity before 2026.1.2 arbitrary file access was possible via the Perforce VCS integration jetbrains · teamcity 2026-07-10 high7.1 CVE-2026-53915 In JetBrains GoLand before 2026.1.3 remote code execution was possible via untrusted project configuration jetbrains · goland 2026-06-19 high7.6 CVE-2026-49374 In JetBrains TeamCity before 2026.1 improper permission checks exposed build configuration parameters jetbrains · teamcity 2026-05-29 high7.1 CVE-2026-49373 In JetBrains TeamCity before 2026.1 remote code execution was possible via Perforce connection settings jetbrains · teamcity 2026-05-29 high7.5 CVE-2026-49372 In JetBrains TeamCity before 2026.1, 2025.11.5 unauthenticated SSRF via build status was possible jetbrains · teamcity 2026-05-29 high7.1 CVE-2026-49371 In JetBrains TeamCity before 2026.1.1 reflected XSS in the keyword filter was possible jetbrains · teamcity 2026-05-29 high8.7 CVE-2026-49368 In JetBrains YouTrack before 2026.1.13162 stored XSS in project notification templates was possible jetbrains · youtrack 2026-05-29 high8.0 CVE-2026-49367 In JetBrains IntelliJ IDEA before 2026.1.1 command execution was possible via the guest user account jetbrains · intellij_idea 2026-05-29 high7.8 CVE-2026-49366 In JetBrains IntelliJ IDEA before 2026.1.1 command injection was possible via filename completion jetbrains · intellij_idea 2026-05-29 high8.2 CVE-2026-44413 In JetBrains TeamCity before 2026.1 2025.11.5 authenticated users could expose server API to unauthorised access jetbrains · teamcity 2026-05-11 high7.4 CVE-2026-41882 In JetBrains IntelliJ IDEA before 2024.3.7.1, 2025.1.7.1, 2025.2.6.2, 2025.3.4.1, 2026.1.1 reading arbitrary local files was possible via built-in web server jetbrains · intellij_idea 2026-04-30 high7.2 CVE-2026-33392 In JetBrains YouTrack before 2025.3.131383 high privileged user can achieve RCE via sandbox bypass jetbrains · youtrack 2026-04-17 high8.8 CVE-2026-28193 In JetBrains YouTrack before 2025.3.121962 apps were able to send requests to the app permissions endpoint jetbrains · youtrack 2026-02-25 high8.2 CVE-2026-25847 In JetBrains PyCharm before 2025.3.2 a DOM-based XSS on Jupyter viewer page was possible jetbrains · pycharm 2026-02-09 high8.1 CVE-2025-64685 In JetBrains YouTrack before 2025.3.104432 missing TLS certificate validation enabled data disclosure jetbrains · youtrack 2025-11-10 high8.4 CVE-2025-64456 In JetBrains ReSharper before 2025.2.4 missing signature verification in DPA Collector allows local privilege escalation jetbrains · resharper 2025-11-10 high8.3 CVE-2025-59458 In JetBrains Junie before 252.284.66, 251.284.66, 243.284.66, 252.284.61, 251.284.61, 243.284.61, 252.284.50, 252.284.54, 251.284.54, 251.284.50, 243.284.54, 2… jetbrains · junie 2025-09-17 high7.7 CVE-2025-59457 In JetBrains TeamCity before 2025.07.2 missing Git URL validation allowed credential leakage on Windows jetbrains · teamcity 2025-09-17 high8.1 CVE-2025-58334 In JetBrains IDE Services before 2025.5.0.1086, 2025.4.2.2164 users without appropriate permissions could assign high-privileged role for themselves jetbrains · ide_services 2025-08-28 high7.5 CVE-2025-57732 In JetBrains TeamCity before 2025.07.1 privilege escalation was possible due to incorrect directory ownership jetbrains · teamcity 2025-08-20 high8.7 CVE-2025-57731 In JetBrains YouTrack before 2025.2.92387 stored XSS was possible via Mermaid diagram content jetbrains · youtrack 2025-08-20 high7.7 CVE-2025-54531 In JetBrains TeamCity before 2025.07 path traversal was possible via plugin unpacking on Windows jetbrains · teamcity 2025-07-28 high7.5 CVE-2025-54530 In JetBrains TeamCity before 2025.07 privilege escalation was possible due to incorrect directory permissions jetbrains · teamcity 2025-07-28

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.