NetSight

Security Dashboard

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

Reset
600 matching advisories · page 7 of 20Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.6 CVE-2025-67499 CNA Plugins Portmap nftables backend can intercept non-local traffic go · github.com/containernetworking/plugins 2025-12-09 high7.4 CVE-2025-66623 Strimzi allows unrestricted access to all Secrets in the same Kubernetes namespace from Kafka Connect and MirrorMaker 2 operands maven · io.strimzi:strimzi 2025-12-05 high7.5 CVE-2025-66564 Sigstore Timestamp Authority allocates excessive memory during request parsing go · github.com/sigstore/timestamp-authority 2025-12-04 high7.5 CVE-2025-66506 Fulcio allocates excessive memory during token parsing go · github.com/sigstore/fulcio 2025-12-04 medium4.7 CVE-2025-20765 In aee daemon, there is a possible system crash due to a race condition. linuxfoundation · yocto, google · android, openwrt · openwrt 2025-12-02 low3.3 CVE-2025-63396 An issue was discovered in PyTorch v2.5 and v2.7.1. linuxfoundation · pytorch 2025-11-12 medium6.9 CVE-2025-64329 containerd CRI server: Host memory exhaustion through Attach goroutine leak go · github.com/containerd/containerd, go · github.com/containerd/containerd/v2 2025-11-06 high7.3 CVE-2024-25621 containerd affected by a local privilege escalation via wide permissions on CRI directory go · github.com/containerd/containerd, go · github.com/containerd/containerd/v2 2025-11-06 high7.3 CVE-2025-52881 runc container escape and denial of service due to arbitrary write gadgets and procfs write redirects go · github.com/opencontainers/runc, go · github.com/opencontainers/selinux 2025-11-05 high7.3 CVE-2025-52565 runc container escape with malicious config due to /dev/console mount and related races go · github.com/opencontainers/runc 2025-11-05 high7.3 CVE-2025-31133 runc container escape via "masked path" abuse due to mount race conditions go · github.com/opencontainers/runc 2025-11-05 medium6.7 CVE-2025-20747 In gnss service, there is a possible out of bounds write due to an incorrect bounds check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +2 2025-11-04 medium6.7 CVE-2025-20746 In gnss service, there is a possible out of bounds write due to an incorrect bounds check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +2 2025-11-04 medium6.7 CVE-2025-20730 In preloader, there is a possible escalation of privilege due to an insecure default value. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2025-11-04 high7.5 CVE-2025-55560 An issue in pytorch v2.7.0 can lead to a Denial of Service (DoS) when a PyTorch model consists of torch.Tensor.to_sparse() and torch.Tensor.to_dense() and is c… linuxfoundation · pytorch 2025-09-25 high7.5 CVE-2025-55558 A buffer overflow occurs in pytorch v2.7.0 when a PyTorch model consists of torch.nn.Conv2d, torch.nn.functional.hardshrink, and torch.Tensor.view-torch.mv() a… linuxfoundation · pytorch 2025-09-25 high7.5 CVE-2025-55557 A Name Error occurs in pytorch v2.7.0 when a PyTorch model consists of torch.cummin and is compiled by Inductor, leading to a Denial of Service (DoS). linuxfoundation · pytorch 2025-09-25 medium5.3 CVE-2025-55554 pytorch v2.8.0 was discovered to contain an integer overflow in the component torch.nan_to_num-.long(). linuxfoundation · pytorch 2025-09-25 high7.5 CVE-2025-55553 A syntax error in the component proxy_tensor.py of pytorch v2.7.0 allows attackers to cause a Denial of Service (DoS). linuxfoundation · pytorch 2025-09-25 high7.5 CVE-2025-55552 pytorch v2.8.0 was discovered to display unexpected behavior when the components torch.rot90 and torch.randn_like are used together. linuxfoundation · pytorch 2025-09-25 high7.5 CVE-2025-55551 An issue in the component torch.linalg.lu of pytorch v2.8.0 allows attackers to cause a Denial of Service (DoS) when performing a slice operation. linuxfoundation · pytorch 2025-09-25 medium5.3 CVE-2025-46153 PyTorch before 3.7.0 has a bernoulli_p decompose function in decompositions.py even though it lacks full consistency with the eager CPU implementation, negativ… linuxfoundation · pytorch 2025-09-25 medium5.3 CVE-2025-46152 In PyTorch before 2.7.0, bitwise_right_shift produces incorrect output for certain out-of-bounds values of the "other" argument. linuxfoundation · pytorch 2025-09-25 medium5.3 CVE-2025-46150 In PyTorch before 2.7.0, when torch.compile is used, FractionalMaxPool2d has inconsistent results. linuxfoundation · pytorch 2025-09-25 medium5.3 CVE-2025-46149 In PyTorch before 2.7.0, when inductor is used, nn.Fold has an assertion error. linuxfoundation · pytorch 2025-09-25 medium5.3 CVE-2025-46148 In PyTorch through 2.6.0, when eager is used, nn.PairwiseDistance(p=2) produces incorrect results. linuxfoundation · pytorch 2025-09-25 medium3.7 CVE-2025-59410 DragonFly's tiny file download uses hard coded HTTP protocol go · github.com/dragonflyoss/dragonfly, go · d7y.io/dragonfly/v2 2025-09-17 medium5.5 CVE-2025-59354 DragonFly has weak integrity checks for downloaded files go · github.com/dragonflyoss/dragonfly, go · d7y.io/dragonfly/v2 2025-09-17 high7.7 CVE-2025-59353 DragonFly's manager generates mTLS certificates for arbitrary IP addresses go · github.com/dragonflyoss/dragonfly, go · d7y.io/dragonfly/v2 2025-09-17 critical9.8 CVE-2025-59352 DragonFly vulnerable to arbitrary file read and write on a peer machine go · github.com/dragonflyoss/dragonfly, go · d7y.io/dragonfly/v2 2025-09-17

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.