NetSight

Security Dashboard

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

Reset
122 matching advisories · page 3 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low2.6 CVE-2026-57926 In JetBrains YouTrack before 2026.2.16593 the websandbox bridge was vulnerable to a prototype pollution attack jetbrains · youtrack 2026-06-26 low3.1 CVE-2026-57922 In JetBrains YouTrack before 2026.2.16593 project settings disclosure via the MCP was possible jetbrains · youtrack 2026-06-26 low3.3 CVE-2026-49383 In JetBrains IntelliJ IDEA before 2026.1 xXE in the UI Designer form parser was possible jetbrains · intellij_idea 2026-05-29 low3.4 CVE-2026-49381 In JetBrains TeamCity before 2026.1 stored XSS on the SAML login page was possible jetbrains · teamcity 2026-05-29 low3.1 CVE-2026-49380 In JetBrains TeamCity before 2026.1 open redirect in the SAML plugin was possible jetbrains · teamcity 2026-05-29 low3.4 CVE-2026-49370 In JetBrains YouTrack before 2026.1.13162 information disclosure was possible on fetchApp requests jetbrains · youtrack 2026-05-29 low2.3 CVE-2026-28196 In JetBrains TeamCity before 2025.11.3 disabling versioned settings left a credentials config on disk jetbrains · teamcity 2026-02-25 low2.7 CVE-2025-68164 In JetBrains TeamCity before 2025.11 port enumeration was possible via the Perforce connection test jetbrains · teamcity 2025-12-16 low3.5 CVE-2025-68163 In JetBrains TeamCity before 2025.11 stored XSS was possible on agentpushInstall page jetbrains · teamcity 2025-12-16 low2.7 CVE-2025-68162 In JetBrains TeamCity before 2025.11 maven embedder allowed loading extensions via project configuration jetbrains · teamcity 2025-12-16 low3.8 CVE-2025-67742 In JetBrains TeamCity before 2025.11 path traversal was possible via file upload jetbrains · teamcity 2025-12-11 low2.7 CVE-2025-67740 In JetBrains TeamCity before 2025.11 improper access control could expose GitHub App token's metadata jetbrains · teamcity 2025-12-11 low3.1 CVE-2025-67739 In JetBrains TeamCity before 2025.11.2 improper repository URL validation could lead to local paths disclosure jetbrains · teamcity 2025-12-11 low2.7 CVE-2025-64773 In JetBrains YouTrack before 2025.3.104432 a race condition allowed bypass of helpdesk Agent limit jetbrains · youtrack 2025-11-11 low2.7 CVE-2025-64682 In JetBrains Hub before 2025.3.104432 a race condition allowed bypass of the Agent-user limit jetbrains · hub 2025-11-10 low2.7 CVE-2025-64681 In JetBrains Hub before 2025.3.104992 a race condition allowed bypass of the user limit via invitations jetbrains · hub 2025-11-10 low3.7 CVE-2025-54529 In JetBrains TeamCity before 2025.07 a CSRF was possible in external OAuth login integration jetbrains · teamcity 2025-07-28 low3.5 CVE-2025-46618 In JetBrains TeamCity before 2025.03.1 stored XSS was possible on Data Directory tab jetbrains · teamcity 2025-04-25 low3.3 CVE-2025-32054 In JetBrains IntelliJ IDEA before 2024.3, 2024.2.4 source code could be logged in the idea.log file jetbrains · intellij_idea 2025-04-03 low2.7 CVE-2025-31141 In JetBrains TeamCity before 2025.03 exception could lead to credential leakage on Cloud Profiles page jetbrains · teamcity 2025-03-27 low3.5 CVE-2024-54158 In JetBrains YouTrack before 2024.3.52635 potential spoofing attack was possible via lack of Punycode encoding jetbrains · youtrack 2024-12-04 low3.7 CVE-2024-54155 In JetBrains YouTrack before 2024.3.51866 improper access control allowed listing of project names during app import without authentication jetbrains · youtrack 2024-12-04 low3.1 CVE-2024-54153 In JetBrains YouTrack before 2024.3.51866 unauthenticated database backup download was possible via vulnerable query parameter jetbrains · youtrack 2024-12-04 low3.5 CVE-2024-47951 In JetBrains TeamCity before 2024.07.3 stored XSS was possible via server global settings jetbrains · teamcity 2024-10-08 low3.5 CVE-2024-47950 In JetBrains TeamCity before 2024.07.3 stored XSS was possible in Backup configuration settings jetbrains · teamcity 2024-10-08 low3.3 CVE-2024-46970 In JetBrains IntelliJ IDEA before 2024.1 hTML injection via the project name was possible jetbrains · intellij_idea 2024-09-16 low3.5 CVE-2024-43809 In JetBrains TeamCity before 2024.07.1 reflected XSS was possible on the agentPushPreset page jetbrains · teamcity 2024-08-16 low3.7 CVE-2024-43808 In JetBrains TeamCity before 2024.07.1 self XSS was possible in the HashiCorp Vault plugin jetbrains · teamcity 2024-08-16 low3.5 CVE-2024-41829 In JetBrains TeamCity before 2024.07 an OAuth code for JetBrains Space could be stolen via Space Application connection jetbrains · teamcity 2024-07-22 low2.6 CVE-2024-41828 In JetBrains TeamCity before 2024.07 comparison of authorization tokens took non-constant time jetbrains · teamcity 2024-07-22

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.