NetSight

Security Dashboard

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

Reset
284 matching advisories · page 6 of 10Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-4hw6-mxq3-gwvg Malicious code in masknvidia (PyPI)Malware pip · masknvidia 2026-07-21 critical GHSA-vx53-hfcm-m5pj Malicious code in libvmnvidia (PyPI)Malware pip · libvmnvidia 2026-07-21 critical GHSA-737q-6w7m-vrqv Malicious code in libvirtualnvidiamask (PyPI)Malware pip · libvirtualnvidiamask 2026-07-21 critical GHSA-q6c5-gm26-wfh2 Malicious code in libverpipnvidia (PyPI)Malware pip · libverpipnvidia 2026-07-21 critical GHSA-p3cj-cjc9-cgp8 Malicious code in liburlnvidiapep (PyPI)Malware pip · liburlnvidiapep 2026-07-21 critical GHSA-3w9q-mw63-5p86 Malicious code in libreplacenvidiapost (PyPI)Malware pip · libreplacenvidiapost 2026-07-21 critical GHSA-8p6f-7hwr-4xjw Malicious code in libreplacecraftnvidia (PyPI)Malware pip · libreplacecraftnvidia 2026-07-21 critical GHSA-pjpq-6r62-5ch2 Malicious code in libpywintnvidia (PyPI)Malware pip · libpywintnvidia 2026-07-21 critical GHSA-w379-m486-93q3 Malicious code in libpipnvidia (PyPI)Malware pip · libpipnvidia 2026-07-21 critical GHSA-2gww-vx74-367m Malicious code in libpaypalpingnvidia (PyPI)Malware pip · libpaypalpingnvidia 2026-07-21 critical GHSA-j63q-232x-q5g7 Malicious code in libosintnvidiapull (PyPI)Malware pip · libosintnvidiapull 2026-07-21 critical GHSA-8m4j-6gj9-p6pq Malicious code in libnvidiamcver (PyPI)Malware pip · libnvidiamcver 2026-07-21 critical GHSA-r8m8-7976-qrhx Malicious code in libnvidiapippaypal (PyPI)Malware pip · libnvidiapippaypal 2026-07-21 critical GHSA-j8rj-hphw-387q Malicious code in libnvidiapy (PyPI)Malware pip · libnvidiapy 2026-07-21 critical GHSA-8p65-x7fx-v6mp Malicious code in libnvidiapeppull (PyPI)Malware pip · libnvidiapeppull 2026-07-21 critical GHSA-45p3-mmph-rm35 Malicious code in libnvidiarecontrol (PyPI)Malware pip · libnvidiarecontrol 2026-07-21 critical GHSA-5xjm-qf58-4wx4 Malicious code in libnvidiareplacerandom (PyPI)Malware pip · libnvidiareplacerandom 2026-07-21 critical GHSA-fjp2-fcpp-qr2q Malicious code in libnvidiasplitpep (PyPI)Malware pip · libnvidiasplitpep 2026-07-21 critical GHSA-5jjq-9w9f-4mvm Malicious code in libnvidiamcad (PyPI)Malware pip · libnvidiamcad 2026-07-21 critical GHSA-cq5v-9j9m-rmc3 Malicious code in libnvidiavmad (PyPI)Malware pip · libnvidiavmad 2026-07-21 critical GHSA-8xc5-53w3-5fm8 Malicious code in libnvidiaencodehacked (PyPI)Malware pip · libnvidiaencodehacked 2026-07-21 critical GHSA-5h3f-rv4h-gcjj Malicious code in libminenvidiahydra (PyPI)Malware pip · libminenvidiahydra 2026-07-21 critical GHSA-cw9j-pxg5-pvp9 Malicious code in libnvidiagrand (PyPI)Malware pip · libnvidiagrand 2026-07-21 critical GHSA-jp7q-j4cr-m7mq Malicious code in libnvidiacpustr (PyPI)Malware pip · libnvidiacpustr 2026-07-21 critical GHSA-9897-rg67-88jg Malicious code in libnvidiacvmc (PyPI)Malware pip · libnvidiacvmc 2026-07-21 critical GHSA-cq6c-c87v-w7p6 Malicious code in libnvidiaintmine (PyPI)Malware pip · libnvidiaintmine 2026-07-21 critical GHSA-3rhg-9fm3-5g96 Malicious code in liblgtbnvidiacontrol (PyPI)Malware pip · liblgtbnvidiacontrol 2026-07-21 critical GHSA-wmcr-rc29-jh47 Malicious code in liblgtbnvidiaproof (PyPI)Malware pip · liblgtbnvidiaproof 2026-07-21 critical GHSA-523j-68rw-4747 Malicious code in libintnvidiagame (PyPI)Malware pip · libintnvidiagame 2026-07-21 critical GHSA-p79p-v47j-jxw3 Malicious code in libhydracvnvidia (PyPI)Malware pip · libhydracvnvidia 2026-07-21

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.