NetSight

Security Dashboard

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

Reset
813 matching advisories · page 7 of 28Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-47615 NVIDIA Dynamo for Linux contains a vulnerability where an attacker may cause server-side request forgery by supplying a crafted URL in a multimodal request. nvidia · dynamo 2026-08-04 high7.5 CVE-2026-47614 NVIDIA Dynamo for Linux contains a vulnerability where an attacker may cause server-side request forgery. nvidia · dynamo 2026-08-04 high7.5 CVE-2026-47613 NVIDIA Dynamo for Linux contains a vulnerability where an attacker may cause improper limitation of a pathname to a restricted directory by supplying a crafted… nvidia · dynamo 2026-08-04 high7.5 CVE-2026-47612 NVIDIA Dynamo for Linux contains a vulnerability in the image loading component where an attacker may cause improper limitation of a pathname to a restricted d… nvidia · dynamo 2026-08-04 high7.5 CVE-2026-24255 NVIDIA Dynamo for Linux contains a vulnerability in the multimodal embedding cache, where an attacker could cause a hash collision by submitting images that sh… nvidia · dynamo 2026-08-04 high8.2 CVE-2026-24253 NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause an out-of-bounds write. nvidia · dynamo 2026-08-04 high8.2 CVE-2026-47483 NVIDIA DCGM Exporter for all platforms contains a vulnerability in the /debug/pprof endpoints, where an attacker could cause uncontrolled resource consumption … 2026-07-28 high7.8 CVE-2026-24252 NVIDIA NeMo for Linux contains a vulnerability where an attacker may cause OS command injection. nvidia · nemo 2026-07-27 high8.8 CVE-2026-64832 FFmpeg versions 4.4 through 8.1.2 contain a double-free vulnerability in the NVIDIA NVDEC hardware decoder within libavcodec/nvdec.c that allows attackers to t… ffmpeg · ffmpeg 2026-07-22 high7.4 CVE-2026-47473 NVIDIA TensorRT-LLM contains a vulnerability where an attacker could cause a write-what-where condition. 2026-07-14 high7.8 CVE-2026-47472 NVIDIA TensorRT-LLM contains a vulnerability in its inter-process communication layer where an attacker with local same-user access could cause deserialization. 2026-07-14 high7.5 CVE-2026-47471 NVIDIA TensorRT-LLM for any platform contains a vulnerability in tensor deserialization, where an attacker could cause a heap based buffer overflow. 2026-07-14 high7.8 CVE-2026-24272 NVIDIA TensorRT contains a vulnerability where an attacker might cause an overflow to a heap-based buffer. nvidia · tensorrt 2026-07-14 high7.8 CVE-2026-24268 NVIDIA TensorRT contains a vulnerability where an attacker might cause a heap-based buffer overflow. nvidia · tensorrt 2026-07-14 high7.8 CVE-2026-24238 NVIDIA TensorRT for contains a vulnerability where an attacker might cause an improper validation of array index. nvidia · tensorrt 2026-07-14 high8.4 CVE-2026-24233 NVIDIA TensorRT-LLM for Linux contains a vulnerability in the restricted unpickler used for model weight deserialization, where a local, unauthenticated attack… 2026-07-14 high7.3 CVE-2026-24229 NVIDIA TensorRT-LLM for Linux contains a vulnerability in the disaggregated orchestrator component, where an attacker could read, write, or delete internal clu… 2026-07-14 high7.5 CVE-2026-47482 NVIDIA Triton Inference Server for Linux contains a vulnerability where an attacker can cause missing release of memory after effective lifetime. 2026-07-14 high7.5 CVE-2026-47480 NVIDIA Triton Inference Server for Linux contains a vulnerability where an attacker can cause an uncaught exception. 2026-07-14 high7.5 CVE-2026-47479 NVIDIA Triton Inference Server for Linux contains a vulnerability where an attacker can cause uncontrolled resource consumption. 2026-07-14 high7.5 CVE-2026-47478 NVIDIA Triton Inference Server for Linux contains a vulnerability where an attacker can cause the use of an expired file descriptor. 2026-07-14 high7.5 CVE-2026-47477 NVIDIA Triton Inference Server for Linux contains a vulnerability where an attacker can cause a stack-based buffer overflow. 2026-07-14 high7.5 CVE-2026-47476 NVIDIA Triton Inference Server for Linux contains a vulnerability where an attacker can cause uncontrolled resource consumption. nvidia · triton_inference_server 2026-07-14 high7.5 CVE-2026-24264 NVIDIA Triton Inference Server for Linux contains a vulnerability where an attacker can cause improper handling of highly compressed data. nvidia · triton_inference_server 2026-07-01 high8.5 CVE-2026-24260 NVIDIA Container Toolkit for Linux contains a vulnerability where an attacker could cause a time-of-check time-of-use race condition. 2026-07-01 high7.8 CVE-2026-24251 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-24250 NVIDIA Megatron Bridge for Linux contains a vulnerability where an attacker could cause improper validation of allowed inputs. nvidia · nemo_megatron_bridge 2026-07-01 high7.8 CVE-2026-24249 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-24248 NVIDIA Megatron Bridge for Linux contains a vulnerability where an attacker could cause improper control of code generation. nvidia · nemo_megatron_bridge 2026-07-01 high7.8 CVE-2026-24247 NVIDIA Megatron Bridge for Linux contains a vulnerability where an attacker could cause deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-07-01

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.