NetSight

Security Dashboard

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

Reset
300 matching advisories · page 4 of 10Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
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 medium5.5 CVE-2025-59351 DragonFly vulnerable to panics due to nil pointer dereference when using variables created alongside an error go · github.com/dragonflyoss/dragonfly, go · d7y.io/dragonfly/v2 2025-09-17 medium5.5 CVE-2025-59350 Dragonfly vulnerable to timing attacks against Proxy’s basic authentication go · github.com/dragonflyoss/dragonfly, go · d7y.io/dragonfly/v2 2025-09-17 medium5.5 CVE-2025-59347 Dragonfly's manager makes requests to external endpoints with disabled TLS authentication go · github.com/dragonflyoss/dragonfly, go · d7y.io/dragonfly/v2 2025-09-17 medium6.8 CVE-2025-20696 In DA, there is a possible out of bounds write due to a missing bounds check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +2 2025-08-04 medium6.5 CVE-2025-20693 In wlan STA driver, there is a possible out of bounds read due to an incorrect bounds check. linuxfoundation · yocto, mediatek · software_development_kit, google · android +1 2025-07-08 medium6.3 CVE-2025-5150 docarray prototype pollution pip · docarray 2025-05-25 medium3.3 CVE-2025-3730 PyTorch Improper Resource Shutdown or Release vulnerability pip · torch 2025-04-16 medium6.8 CVE-2025-20656 In DA, there is a possible out of bounds write due to a missing bounds check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +9 2025-04-07 medium5.3 CVE-2025-3001 PyTorch is vulnerable to memory corruption through its torch.lstm_cell function pip · torch 2025-03-31 medium5.3 CVE-2025-3000 PyTorch is vulnerable to memory corruption through its torch.jit.script function pip · torch 2025-03-31 medium5.3 CVE-2025-2999 PyTorch is vulnerable to memory corruption through its unpack_sequence function pip · torch 2025-03-31 medium5.3 CVE-2025-2998 PyTorch is Vulnerable to Memory Consumption through pad_packed_sequence Function pip · torch 2025-03-31 medium4.6 CVE-2024-40635 containerd has an integer overflow in User ID handling go · github.com/containerd/containerd/v2, go · github.com/containerd/containerd 2025-03-17 medium5.0 CVE-2025-2148 PyTorch Tuple Handler is Vulnerable to Memory Corruption through Manipulation of None Argument pip · torch 2025-03-10 medium4.1 CVE-2025-20651 In da, there is a possible out of bounds read due to a missing bounds check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2025-03-03 medium6.8 CVE-2025-20650 In da, there is a possible out of bounds write due to a missing bounds check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2025-03-03 medium6.6 CVE-2025-20635 In V6 DA, there is a possible out of bounds write due to a missing bounds check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2025-02-03 medium5.3 CVE-2024-20147 In Bluetooth FW, there is a possible reachable assertion due to improper exception handling. linuxfoundation · yocto, mediatek · software_development_kit, google · android +1 2025-02-03 medium6.5 CVE-2023-37038 A Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486… linuxfoundation · magma 2025-01-21 medium6.5 CVE-2023-37037 A Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486… linuxfoundation · magma 2025-01-21 medium6.5 CVE-2023-37036 A Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486… linuxfoundation · magma 2025-01-21 medium6.5 CVE-2023-37034 A Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486… linuxfoundation · magma 2025-01-21 medium6.5 CVE-2023-37033 A Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486… linuxfoundation · magma 2025-01-21 medium6.5 CVE-2023-37031 A Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486… linuxfoundation · magma 2025-01-21 medium6.5 CVE-2023-37030 A Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486… linuxfoundation · magma 2025-01-21

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.