NetSight

Security Dashboard

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

Reset
441 matching advisories · page 3 of 15Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.1 CVE-2026-65127 NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker could cause exposure of sensitive system information due to uncleared deb… nvidia · infra_controller 2026-09-22 medium5.0 CVE-2026-65126 NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker could cause improper enforcement of a behavioral workflow. nvidia · infra_controller 2026-09-22 medium6.6 CVE-2026-65125 NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker could cause external control of a file name or path. nvidia · infra_controller 2026-09-22 medium5.9 CVE-2026-65124 NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker could cause an XML injection. nvidia · infra_controller 2026-09-22 medium5.0 CVE-2026-65117 NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker could cause use of a hard-coded password. nvidia · infra_controller 2026-09-22 medium6.5 CVE-2026-65115 NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker may cause uncontrolled resource consumption. nvidia · infra_controller 2026-09-22 medium6.5 CVE-2026-65112 NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker could cause uncontrolled resource consumption. nvidia · infra_controller 2026-09-22 medium5.5 CVE-2026-65088 NVIDIA NemoClaw contains a vulnerability where an attacker could cause invocation of process using visible sensitive information. nvidia · nemoclaw 2026-08-25 medium5.6 CVE-2026-65087 NVIDIA NemoClaw contains a vulnerability where an attacker could cause insufficiently protected credentials . nvidia · nemoclaw 2026-08-25 medium6.8 CVE-2026-65086 NVIDIA OpenShell for Linux contains a vulnerability in its sandbox exec handler, where an attacker could cause an OS command injection. nvidia · openshell 2026-08-25 medium5.2 CVE-2026-65085 NVIDIA OpenShell for Linux contains a vulnerability in its inference proxy, where an attacker could cause an improper encoding or escaping of output. nvidia · openshell 2026-08-25 medium6.0 CVE-2026-47624 NVIDIA DGX Spark contains a vulnerability in UEFI where a Attacker may cause a/an CWE-693 by privileged local user. nvidia · dgx_spark_uefi 2026-08-25 medium6.0 CVE-2026-24225 NVIDIA DGX Spark contains a vulnerability in the standalone MM firmware where an attacker could be able to cause an out-of-bounds read. nvidia · dgx_spark_uefi 2026-08-25 medium6.8 CVE-2026-24168 NVIDIA UFM Enterprise contains a vulnerability in the IBDiagnet API where an authenticated attacker with administrative privileges may cause command injection … 2026-08-25 medium6.8 CVE-2026-24167 NVIDIA UFM Enterprise contains a vulnerability in the user management component, where an authenticated administrator could inject commands by sending a crafte… 2026-08-25 medium5.1 CVE-2026-24166 NVIDIA UFM Enterprise contains a vulnerability in the session management component, where an attacker could use a hard-coded cryptographic key to extract infor… 2026-08-25 medium5.5 CVE-2026-47630 NVIDIA Triton Inference Server for Linux contains a vulnerability where an attacker could cause an absolute path traversal. nvidia · triton_inference_server 2026-08-18 medium6.5 CVE-2026-47606 NVIDIA Triton Inference Server for Linux contains a vulnerability where an attacker could cause an absolute path traversal. nvidia · triton_inference_server 2026-08-18 medium5.3 CVE-2026-47622 NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause the generation of error messages that contain sensitive information. nvidia · dynamo 2026-08-04 medium6.5 CVE-2026-47621 NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause a race condition in the LoRA manager singleton initialization. nvidia · dynamo 2026-08-04 medium6.5 CVE-2026-47620 NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause a race condition in the LoRA manager singleton initialization. nvidia · dynamo 2026-08-04 medium6.6 CVE-2026-47619 NVIDIA Dynamo for Linux examples and recipes contain a vulnerability where an attacker could cause a system failure. nvidia · dynamo 2026-08-04 medium4.4 CVE-2026-47487 NVIDIA Triton Inference Server for Linux contains a vulnerability where a user could cause files outside the model repository to be read, written to, or modifi… nvidia · triton_inference_server 2026-08-04 medium4.3 CVE-2026-24232 NVIDIA Tranformers4Rec contains a vulnerability where an attacker could cause improper deserialization of untrusted data. 2026-07-21 medium6.2 CVE-2026-47475 NVIDIA TensorRT-LLM contains a vulnerability in the OpenAI-compatible inference API where an attacker could trigger a reachable assertion in the sampler thread. 2026-07-14 medium6.2 CVE-2026-47470 NVIDIA TensorRT-LLM for any platform contains a vulnerability in the gRPC server chat API endpoint, where an attacker could cause CWE-20 by local attack. 2026-07-14 medium6.2 CVE-2026-24271 NVIDIA TensorRT-LLM contains a vulnerability in the OpenAI-compatible inference API, where an attacker could cause allocation of GPU resources without limits o… 2026-07-14 medium6.4 CVE-2026-24259 NVIDIA TensorRT-LLM for Linux contains a vulnerability where an attacker could cause missing authentication for a critical function. 2026-07-14 medium6.8 CVE-2026-24234 NVIDIA TensorRT-LLM for Linux contains a vulnerability in the multimodal media fetching functions, where a network-accessible attacker could cause server-side … 2026-07-14 medium5.3 CVE-2026-24227 NVIDIA TensorRT for contains a vulnerability where a user might cause a deserialization of untrusted data. nvidia · tensorrt 2026-07-14

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.