NetSight

Security Dashboard

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

Reset
1,592 matching advisories · page 7 of 54Index 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 high8.2 CVE-2026-65121 NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker could cause an improper authentication issue. nvidia · infra_controller 2026-09-22 high7.5 CVE-2026-65118 NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker could cause improper certificate validation. 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 high8.3 CVE-2026-65114 NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker could cause missing authentication for a critical function. nvidia · infra_controller 2026-09-22 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 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 high7.8 CVE-2026-65111 NVIDIA NeMo Speech for all platforms contains a vulnerability where malicious input created by an attacker could cause a code injection. nvidia · nemo_speech 2026-09-22 high7.8 CVE-2026-24267 NVIDIA NeMo Speech for all platforms contains a vulnerability in the speech data explorer component, where malicious data created by an attacker could cause re… nvidia · nemo_speech 2026-09-22 high7.8 CVE-2026-24239 NVIDIA NeMo Speech for all platforms contains a vulnerability where malicious data created by an attacker could cause remote code execution. nvidia · nemo_speech 2026-09-22 high7.5 CVE-2026-47625 NVIDIA Triton Inference Server for Linux contains a vulnerability where an attacker could abuse missing authorization. 2026-09-08 high7.5 CVE-2026-16497 NVIDIA Triton Inference Server for Linux contains a vulnerability where an attacker could cause excessive iteration. 2026-09-08 high7.8 CVE-2026-61779 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-01 high7.8 CVE-2026-61778 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-01 high7.8 CVE-2026-61777 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-01 high7.8 CVE-2026-61776 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-01 high7.8 CVE-2026-61775 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-01 high7.8 CVE-2026-61774 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-01 high7.8 CVE-2026-61773 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-01 high7.8 CVE-2026-61772 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-01 high7.8 CVE-2026-61771 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-01 high7.8 CVE-2026-61770 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-01 high7.8 CVE-2026-61769 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-01 high7.8 CVE-2026-61768 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-01 high7.8 CVE-2026-61767 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-01 high7.8 CVE-2026-61766 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-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.