NetSight

Security Dashboard

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

Reset
284 matching advisories · page 1 of 10Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.0 CVE-2026-65094 NVIDIA VIRTIO-Net for Bluefield contains a vulnerability in Virtio-Net where a VM user may cause a Write-What-Where condition by crafted message. NVIDIA · VIRTIO-Net GA, NVIDIA · VIRTIO-Net LTS25, NVIDIA · VIRTIO-Net LTS24 +1 2 days ago critical10.0 CVE-2026-65145 NVIDIA NeMo Agent Toolkit contains a vulnerability where a attacker could cause a missing authentication issue. 25 days ago critical9.1 CVE-2026-65173 NVIDIA AIStore for Linux contains a missing authentication vulnerability in the token-revocation endpoint where an unauthenticated remote attacker may submit c… 39 days ago critical10.0 CVE-2026-65162 NVIDIA AIStore for Linux contains a vulnerability in the legacy ETL Kubernetes PodSpec initialization API where a remote attacker may supply Kubernetes host-na… 39 days ago critical9.8 CVE-2026-65113 NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker could cause use of hard-coded credentials. nvidia · infra_controller 2026-09-22 critical9.9 CVE-2026-65093 NVIDIA OpenShell for Linux contains a vulnerability where an attacker could cause a sandbox escape. nvidia · openshell 2026-08-25 critical9.9 CVE-2026-65083 NVIDIA OpenShell for Linux contains a vulnerability in its sandbox provisioning API, where an attacker could cause an incomplete list of disallowed inputs. nvidia · openshell 2026-08-25 critical9.8 CVE-2026-47627 NVIDIA Triton Inference Server for Linux contains a vulnerability where an attacker could cause path traversal. nvidia · triton_inference_server 2026-08-18 critical9.9 CVE-2026-63298 An improper neutralization of special elements vulnerability in LXD's NVIDIA instance configuration handling allows an authenticated attacker to inject arbitra… canonical · lxd 2026-08-12 critical9.8 CVE-2026-24254 NVIDIA Dynamo for Linux contains a vulnerability in the multimodal serving topology, where an attacker could cause an out-of-bounds write. nvidia · dynamo 2026-08-04 critical GHSA-hp56-rwf9-7fpm Malicious code in vmnvidia (PyPI)Malware pip · vmnvidia 2026-07-21 critical GHSA-vxc7-w52w-8w3w Malicious code in vernvidia (PyPI)Malware pip · vernvidia 2026-07-21 critical GHSA-729m-4g63-xr58 Malicious code in urlnvidia (PyPI)Malware pip · urlnvidia 2026-07-21 critical GHSA-x2w9-2www-m2f4 Malicious code in tpstrintnvidia (PyPI)Malware pip · tpstrintnvidia 2026-07-21 critical GHSA-r8r7-w8wv-fm5h Malicious code in tppylgtbnvidia (PyPI)Malware pip · tppylgtbnvidia 2026-07-21 critical GHSA-76vp-hw9c-565x Malicious code in tppostcandynvidia (PyPI)Malware pip · tppostcandynvidia 2026-07-21 critical GHSA-5mh6-fg27-frcr Malicious code in tpproofstringnvidia (PyPI)Malware pip · tpproofstringnvidia 2026-07-21 critical GHSA-55g4-mr5h-cqww Malicious code in tpnvidiapyw (PyPI)Malware pip · tpnvidiapyw 2026-07-21 critical GHSA-g5hm-465h-hmc5 Malicious code in tpnvidiasplit (PyPI)Malware pip · tpnvidiasplit 2026-07-21 critical GHSA-7m9g-qx57-ggw2 Malicious code in tpnvidiaver (PyPI)Malware pip · tpnvidiaver 2026-07-21 critical GHSA-4r8x-gmmh-jcr8 Malicious code in tpnvidiapong (PyPI)Malware pip · tpnvidiapong 2026-07-21 critical GHSA-mj42-q62f-m34j Malicious code in tpnvidiapush (PyPI)Malware pip · tpnvidiapush 2026-07-21 critical GHSA-jc8q-h978-gv79 Malicious code in tpnvidiapephttp (PyPI)Malware pip · tpnvidiapephttp 2026-07-21 critical GHSA-gvg3-2gj7-64cr Malicious code in tpnvidiaintelpush (PyPI)Malware pip · tpnvidiaintelpush 2026-07-21 critical GHSA-v9p9-6pv9-pph4 Malicious code in tpnvidiacv (PyPI)Malware pip · tpnvidiacv 2026-07-21 critical GHSA-8mmh-6c69-2j5x Malicious code in tpnvidiareurl (PyPI)Malware pip · tpnvidiareurl 2026-07-21 critical GHSA-v99j-mfgr-752f Malicious code in tpnvidiarandsplit (PyPI)Malware pip · tpnvidiarandsplit 2026-07-21 critical GHSA-6h89-6j24-6cx5 Malicious code in tpnvidiapullpep (PyPI)Malware pip · tpnvidiapullpep 2026-07-21 critical GHSA-8gmc-25q5-2rhc Malicious code in tpnvidiahttpreplace (PyPI)Malware pip · tpnvidiahttpreplace 2026-07-21 critical GHSA-ggf3-9pvg-25q7 Malicious code in tpnvidiainfopong (PyPI)Malware pip · tpnvidiainfopong 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.