NetSight

Security Dashboard

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

Reset
1,592 matching advisories · page 8 of 54Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2026-61765 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-61764 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-61763 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-61762 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-61761 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-61760 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-61759 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-61758 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-61757 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-61756 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-61755 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-61754 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-61753 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-61752 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-61751 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-61750 NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. nvidia · nemo_megatron_bridge 2026-09-01 high8.1 CVE-2026-65105 NVIDIA NemoClaw for Linux contains a vulnerability in its inference server setup, where a remote attacker may access the inference service without authenticati… nvidia · nemoclaw 2026-08-25 high7.8 CVE-2026-65099 NVIDIA NemoClaw for Linux contains a vulnerability in its command-line interface, where an attacker could cause OS command injection. nvidia · nemoclaw 2026-08-25 high8.1 CVE-2026-65098 NVIDIA NemoClaw for Linux contains a vulnerability in its remote-access helper workflow, where an attacker could cause weak authentication. nvidia · nemoclaw 2026-08-25 high7.5 CVE-2026-65097 NVIDIA NemoClaw for Linux contains a vulnerability in its installation scripts, where an attacker could cause a download of code without integrity check. nvidia · nemoclaw 2026-08-25 high7.8 CVE-2026-65096 NVIDIA NemoClaw for Linux contains a vulnerability in the Telegram bridge component, where an attacker could cause an OS command injection. nvidia · nemoclaw 2026-08-25 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 high8.5 CVE-2026-65092 NVIDIA OpenShell Sandbox for Linux contains a vulnerability where an attacker could cause a path traversal bypass of L7 REST network policy. nvidia · openshell 2026-08-25 high8.8 CVE-2026-65091 NVIDIA OpenShell for all platforms contains a vulnerability where a malicious gateway could cause OS command injection. nvidia · openshell 2026-08-25 high7.8 CVE-2026-65090 NVIDIA NemoClaw for Linux contains a vulnerability in its NIM management component, where an attacker could cause OS command injection. nvidia · nemoclaw 2026-08-25 high7.8 CVE-2026-65089 NVIDIA NemoClaw for Linux contains a vulnerability in its status and logs plugin commands, where an attacker could cause OS command injection. nvidia · nemoclaw 2026-08-25 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

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.