NetSight

Security Dashboard

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

Reset
813 matching advisories · page 8 of 28Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2026-24246 NVIDIA Megatron Bridge for Linux contains a vulnerability where an attacker could cause improper control of dynamically managed code resources. nvidia · nemo_megatron_bridge 2026-07-01 high7.8 CVE-2026-24245 NVIDIA Megatron Bridge for Linux contains a vulnerability where an attacker could cause deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-07-01 high7.8 CVE-2026-24244 NVIDIA Megatron Bridge for Linux contains a vulnerability where an attacker could cause deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-07-01 high7.8 CVE-2026-24243 NVIDIA Megatron Bridge for Linux contains a vulnerability where an attacker could cause deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-07-01 high7.8 CVE-2026-24242 NVIDIA Megatron Bridge for Linux contains a vulnerability where an attacker could cause server-side request forgery. nvidia · nemo_megatron_bridge 2026-07-01 high7.8 CVE-2026-24240 NVIDIA Megatron Bridge for Linux contains a vulnerability where an attacker could cause deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-07-01 high7.8 CVE-2026-24228 NVIDIA NeMo Framework for Linux contains a vulnerability where an attacker may cause deserialization of untrusted data. nvidia · nemo 2026-06-16 high7.8 CVE-2026-24155 NVIDIA NeMo Framework for all platforms contains a code injection vulnerability. nvidia · nemo 2026-06-16 high7.3 CVE-2026-24181 NVIDIA DALI contains a vulnerability in a component where an attacker could cause an improper index validation. nvidia · data_loading_library 2026-06-09 high7.3 CVE-2026-24180 NVIDIA DALI contains a vulnerability in a component where an attacker could cause a heap-based buffer overflow. nvidia · data_loading_library 2026-06-09 high8.2 CVE-2026-48594 Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in elixir-tesla tesla allows a denial of service via decompression bomb in HTTP … erlang · tesla 2026-06-02 high8.2 CVE-2026-48595 Improper Handling of Case Sensitivity vulnerability in elixir-tesla tesla allows credential leakage to a third-party origin on cross-origin redirects. erlang · tesla 2026-06-02 high8.2 CVE-2026-48597 Allocation of Resources Without Limits or Throttling vulnerability in elixir-tesla tesla allows denial of service via atom table exhaustion in Tesla.Adapter.Mi… erlang · tesla 2026-06-02 high7.8 CVE-2026-24237 NVIDIA NVTabular contains a vulnerability where an attacker could cause improper deserialization of untrusted data. nvidia · nvtabular 2026-06-02 high7.8 CVE-2026-24221 NVIDIA NVTabular contains a vulnerability where an attacker could cause improper deserialization of untrusted data. nvidia · nvtabular 2026-06-02 high7.0 CVE-2026-24200 NVIDIA vGPU software contains a vulnerability in the virtual GPU manager, where an attacker could cause a use-after-free for stack memory. 2026-05-26 high7.1 CVE-2026-24196 NVIDIA Display Driver for Linux contains a vulnerability where a user could cause an out-of-bounds read. nvidia · gpu_display_driver 2026-05-26 high7.1 CVE-2026-24195 NVIDIA Display Driver for Linux contains a vulnerability in UVM, where a user could cause improper input validation. nvidia · gpu_display_driver 2026-05-26 high7.8 CVE-2026-24194 NVIDIA Display Driver for Linux contains a vulnerability in a kernel mode layer handler, where a user could cause improper permission handling. nvidia · gpu_display_driver 2026-05-26 high7.8 CVE-2026-24193 NVIDIA Display Driver for Windows and Linux contains a vulnerability where an attacker could cause an out-of-bounds write. nvidia · gpu_display_driver 2026-05-26 high7.8 CVE-2026-24192 NVIDIA Display Driver for Linux contains a vulnerability where an attacker could cause an incorrect conversion between numeric types, leading to a heap buffer … nvidia · gpu_display_driver 2026-05-26 high7.8 CVE-2026-24191 NVIDIA Display Driver for Windows contains a vulnerability where an attacker could cause a time-of-check time-of-use issue. nvidia · gpu_display_driver 2026-05-26 high7.8 CVE-2026-24190 NVIDIA Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where a user could cause improper access to GPU resources. nvidia · gpu_display_driver 2026-05-26 high8.8 CVE-2026-24187 NVIDIA Display Driver for Linux contains a vulnerability where an attacker could cause a use-after-free. nvidia · gpu_display_driver 2026-05-26 high7.5 CVE-2026-24212 NVIDIA Isaac Launchable for Linux contains a vulnerability where sensitive information is transmitted in clear text. nvidia · isaac_launchable 2026-05-26 high7.8 CVE-2026-24162 NVIDIA Transformers4Rec for Linux contains a vulnerability where an attacker could cause improper deserialization of untrusted data. nvidia · transformers4rec 2026-05-26 high8.1 CVE-2026-24218 NVIDIA DGX OS contains a vulnerability in the factory provisioning process, where the cloning of a base image causes identical SSH host keys to be deployed acr… nvidia · dgx_os 2026-05-20 high8.8 CVE-2026-24217 NVIDIA BioNeMo Core for Linux contains a vulnerability where a user could cause a path traversal by loading a malicious file. nvidia · bionemo_framework 2026-05-20 high7.8 CVE-2026-24216 NVIDIA BioNemo for Linux contains a vulnerability where a user could cause a deserialization of untrusted data. nvidia · bionemo_framework 2026-05-20 high8.2 CVE-2026-24188 NVIDIA TensorRT contains a vulnerability where an attacker could cause an out-of-bounds write. nvidia · tensorrt 2026-05-20

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.