NetSight

Security Dashboard

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

Reset
1,707 matching advisories · page 2 of 57Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.4 CVE-2026-62929 Expired pointer dereference in the MigTD's virtio-vsock implementation for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow … n/a · Intel(R) TDX Migration Trust Domain (MigTD) 11 days ago high8.4 CVE-2026-60142 Write-what-where condition in the MigTD for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow an information disclosure and e… n/a · Intel(R) TDX Migration Trust Domain (MigTD) 11 days ago high8.4 CVE-2026-60138 Use of out-of-range pointer offset in the MigTD's virtio-vsock implementation for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may… n/a · Intel(R) TDX Migration Trust Domain (MigTD) 11 days ago high8.8 CVE-2026-57892 Insufficient granularity of access control in the MigTD v2 policy evaluation engine for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervis… n/a · Intel(R) TDX Migration Trust Domain (MigTD) 11 days ago high8.7 CVE-2026-57891 Out-of-bounds write in the XmlCliCommonDxe for the Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP within Ring 0 UEFI may allow an escalation of … n/a · Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP 11 days ago high8.7 CVE-2026-57890 Improper cleanup on thrown exception in the MigTD's SPDM responder for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow an i… n/a · Intel(R) TDX Migration Trust Domain (MigTD) 11 days ago high8.7 CVE-2026-57882 Out-of-bounds write in the XmlCliCommonDxe for the Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP within Ring 0 UEFI may allow an escalation of … n/a · Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP 11 days ago high8.7 CVE-2026-56435 Out-of-bounds write in the XmlCliCommonDxe for the Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP within Ring 0 UEFI may allow an escalation of … n/a · Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP 11 days ago high8.2 CVE-2026-56432 Unintended proxy or intermediary ('confused deputy') in the MigTD signing for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may all… n/a · Intel(R) TDX Migration Trust Domain (MigTD) 11 days ago high8.4 CVE-2026-50175 Untrusted pointer dereference in the FirmwareWakingVector for the Intel(R) Slim Bootloader within Ring 0: Bare Metal OS may allow an escalation of privilege. n/a · Intel(R) Slim Bootloader 11 days ago high7.1 CVE-2026-44382 Out-of-bounds read for some Intel(R) Wireless Bluetooth(R) within Ring 0: Kernel may allow a denial of service. n/a · Intel(R) Wireless Bluetooth(R) 11 days ago high7.1 CVE-2026-42956 Out-of-bounds write for some Intel(R) Wireless Bluetooth(R) within Ring 0: Kernel may allow a denial of service. n/a · Intel(R) Wireless Bluetooth(R) 11 days ago high8.6 CVE-2026-41224 Out-of-bounds write in the UEFI firmware for the Intel(R) Slim Bootloader within Ring 0: Bare Metal OS may allow an escalation of privilege. n/a · Intel(R) Slim Bootloader 11 days ago high8.6 CVE-2026-41221 Integer overflow in the UEFI firmware for the Intel(R) Slim Bootloader within Ring 0: Bare Metal OS may allow an escalation of privilege. n/a · Intel(R) Slim Bootloader 11 days ago high8.5 CVE-2026-40433 Heap-based buffer overflow for some Intel(R) PROSet Wireless Wi-Fi Software for Windows within Ring 0: Kernel may allow a denial of service. n/a · Intel(R) PROSet Wireless Wi-Fi Software for Windows 11 days ago high8.6 CVE-2026-35500 Stack-based buffer overflow in the UEFI firmware for the Intel(R) Slim Bootloader within Ring 0: Bare Metal OS may allow an escalation of privilege. n/a · Intel(R) Slim Bootloader 11 days ago high8.3 CVE-2026-50109 Out-of-bounds write for some Intel(R) Performance Counter Monitor (Intel(R) PCM) within Ring 3: User Applications may allow a denial of service. n/a · Intel(R) Performance Counter Monitor (Intel(R) PCM) 11 days ago high8.5 CVE-2026-34016 Time-of-check time-of-use race condition for the Intel(R) VTune(TM) Profiler software before version 2026.0.0 within Ring 1: Device Drivers may allow an escala… n/a · Intel(R) VTune(TM) Profiler software 11 days ago high8.5 CVE-2026-32670 Time-of-check time-of-use race condition for the Intel(R) VTune(TM) Profiler software within Ring 1: Device Drivers may allow an escalation of privilege. n/a · Intel(R) VTune(TM) Profiler software 11 days ago high8.5 CVE-2026-32667 Out-of-bounds write for the Intel(R) VTune(TM) Profiler software within Ring 1: Device Drivers may allow an escalation of privilege. n/a · Intel(R) VTune(TM) Profiler software 11 days ago high7.3 CVE-2026-124850 A SQL injection vulnerability exists in a database migration script in flowintel. The migration... flowintel · flowintel 12 days ago high7.1 CVE-2026-123842 In JetBrains IntelliJ IDEA before 2026.3 arbitrary file write was possible via symlinks when extracting plugin archives jetbrains · intellij_idea 15 days ago high7.8 CVE-2026-123853 In JetBrains IntelliJ IDEA before 2026.3, 2026.2.2 code execution was possible in Safe Mode via project-controlled JVM options of the build process JetBrains · IntelliJ IDEA 15 days ago high7.0 CVE-2026-123849 In JetBrains IntelliJ IDEA before 2026.3 code execution was possible in untrusted projects via the Terraform File Watchers JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 15 days ago high7.4 CVE-2026-123848 In JetBrains IntelliJ IDEA before 2026.3 host name verification was missing for server TLS certificates JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 15 days ago high7.8 CVE-2026-123841 In JetBrains IntelliJ IDEA before 2026.3 code execution was possible via symlinks in an imported settings archive JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 15 days ago high7.8 CVE-2026-123838 In JetBrains IntelliJ IDEA before 2026.3 code execution was possible in Safe Mode via UI Designer form file JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 15 days ago high7.8 CVE-2026-123837 In JetBrains IntelliJ IDEA before 2026.3, 2026.2.1 command injection was possible in untrusted projects via Tomcat run configurations on WSL JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 15 days ago high7.5 CVE-2026-123305 In JetBrains IntelliJ IDEA before 2026.3 path traversal was possible via unpacking Dev Container archives from a remote host JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 15 days ago high7.4 CVE-2026-123306 In JetBrains IntelliJ IDEA before 2026.3 improper checks allowed server certificates to be added to the trust store during headless runs JetBrains · IntelliJ IDEA, jetbrains · intellij_idea 15 days ago

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.