NetSight

Security Dashboard

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

Reset
122 matching advisories · page 2 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.6 CVE-2026-123833 In JetBrains IntelliJ IDEA before 2026.3 database connections could be established in untrusted projects jetbrains · intellij_idea 15 days ago low3.1 CVE-2026-123337 In JetBrains YouTrack before 2026.2.19656 users without update permission could change issue visibility JetBrains YouTrack 16 days ago low3.1 CVE-2026-123336 In JetBrains YouTrack before 2026.2.19728 the attachment size limit could be bypassed via AI assistant thread conversion JetBrains YouTrack 16 days ago low3.5 CVE-2026-123335 In JetBrains YouTrack before 2026.2.19562, 2026.1.14137, 2025.3.169041 missing authorization allowed attaching tags to any issue via the tag issues collection JetBrains YouTrack 16 days ago low3.8 CVE-2026-123334 In JetBrains YouTrack before 2026.2.19562 project admins of a related project could delete VCS integrations owned by another project JetBrains YouTrack 16 days ago low3.8 CVE-2026-123333 In JetBrains YouTrack before 2026.2.19562 sprint creation allowed moving issues from inaccessible projects between sprints JetBrains YouTrack 16 days ago low3.1 CVE-2026-123314 In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 xXE attack was possible via an XML response to an HTTP Client request jetbrains · intellij_idea 16 days ago low2.7 CVE-2026-123300 In JetBrains Hub before 2026.2.52519 missing authorisation allowed users with read-only access to modify auth module group mappings JetBrains Hub 16 days ago low3.1 CVE-2026-123299 In JetBrains Hub before 2026.2.52519 information disclosure via user search queries was possible JetBrains Hub 16 days ago low2.7 CVE-2026-123292 In JetBrains Datalore before 2026.4 aPI tokens and sessions of removed or banned users remained... jetbrains · datalore 16 days ago low3.1 CVE-2026-123320 In JetBrains Toolbox App before 3.9 insufficient warning in the login dialog allowed connecting to a malicious server JetBrains · Toolbox App 16 days ago low3.7 CVE-2026-123319 In JetBrains Ktor before 3.6.1 missing Domain attribute validation in client cookie storage allowed cookie injection JetBrains · Ktor 16 days ago low3.3 CVE-2026-123313 In JetBrains IntelliJ IDEA before 2026.3 improper checks could enable disabled plugins via external dependency settings JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 16 days ago low3.3 CVE-2026-123312 In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 sSRF was possible via annotations.xml files during indexing JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 16 days ago low2.0 CVE-2026-103489 In JetBrains YouTrack before 2026.2.19422 hTML injection in VCS command failure notifications was possible jetbrains · youtrack 52 days ago low3.1 CVE-2026-100280 In JetBrains YouTrack before 2026.2.19197 creating a project from an unreadable custom template was possible jetbrains · youtrack 52 days ago low2.7 CVE-2026-100271 In JetBrains YouTrack before 2026.2.19197 missing authorisation on several endpoints allowed authenticated users to access information from other projects jetbrains · youtrack 52 days ago low3.3 CVE-2026-100270 In JetBrains YouTrack before 2026.2.19197 low-level Admin Read permission users could disclose integration credentials via import configurations jetbrains · youtrack 52 days ago low2.7 CVE-2026-100264 In JetBrains YouTrack before 2026.2.18991 stored SMTP server credentials could be disclosed by changing the server host jetbrains · youtrack 52 days ago low3.3 CVE-2026-86505 In JetBrains IntelliJ IDEA before 2026.2.2 missing project-trust check leaked project metadata to JetBrains Marketplace jetbrains · intellij_idea 2026-09-07 low3.3 CVE-2026-86503 In JetBrains IntelliJ IDEA before 2026.2.2 opening an untrusted project could trigger SSRF via Kubernetes spec-source URL fetching jetbrains · intellij_idea 2026-09-07 low2.8 CVE-2026-86501 In JetBrains IntelliJ IDEA before 2026.2.2 terminal command input could be written to idea.log jetbrains · intellij_idea 2026-09-07 low3.5 CVE-2026-86491 In JetBrains YouTrack before 2026.2.18634 stored XSS was possible via project and organization icon uploads JetBrains YouTrack 2026-09-07 low3.1 CVE-2026-86487 In JetBrains YouTrack before 2026.2.18634 a crafted WebSocket message allowed read-only whiteboard users to modify canvas content JetBrains YouTrack 2026-09-07 low3.7 CVE-2026-86486 In JetBrains YouTrack before 2026.2.18634 the generic VCS webhook handler failed open when its secret was blank JetBrains YouTrack 2026-09-07 low3.3 CVE-2026-86485 In JetBrains YouTrack before 2026.2.18634 iP spoofing via HTTP headers allowed forged Bitbucket webhooks JetBrains YouTrack 2026-09-07 low3.6 CVE-2026-75052 In JetBrains IntelliJ IDEA before 2026.2.1 command execution via crafted Markdown preview content was possible in trusted projects jetbrains · intellij_idea 2026-08-17 low3.5 CVE-2026-64800 In JetBrains GoLand before 2026.2 sensitive configuration values written to log files by default jetbrains · goland 2026-07-23 low3.5 CVE-2026-61492 In JetBrains YouTrack before 2026.2.17394 stored XSS via article titles in digest emails was possible jetbrains · youtrack 2026-07-10 low3.5 CVE-2026-59791 In JetBrains YouTrack before 2026.2.17012 cSS injection via Mermaid diagram rendering was possible jetbrains · youtrack 2026-07-10

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.