NetSight

Security Dashboard

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

Reset
38 matching advisories · page 1 of 2Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.6 CVE-2026-20435 In preloader, there is a possible read of device unique identifiers due to a logic error. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +2 2026-03-02 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 medium5.5 CVE-2025-20722 In gnss driver, there is a possible out of bounds read due to an integer overflow. rdkcentral · rdk-b, google · android, openwrt · openwrt 2025-10-14 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.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 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 medium6.6 CVE-2024-20145 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-01-06 medium6.6 CVE-2024-20144 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-01-06 medium6.6 CVE-2024-20143 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-01-06 medium6.2 CVE-2024-20136 In da, there is a possible out of bounds read due to a missing bounds check. rdkcentral · rdk-b, google · android, openwrt · openwrt 2024-12-02 medium6.2 CVE-2024-20107 In da, there is a possible out of bounds read due to a missing bounds check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2024-11-04 medium4.4 CVE-2024-20085 In power, there is a possible out of bounds read due to a missing bounds check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2024-09-02 medium4.4 CVE-2024-20084 In power, there is a possible out of bounds read due to a missing bounds check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2024-09-02 medium6.7 CVE-2024-20081 In gnss service, there is a possible out of bounds write due to improper input validation. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2024-07-01 medium6.7 CVE-2024-20056 In preloader, there is a possible escalation of privilege due to an insecure default value. rdkcentral · rdk-b, google · android, openwrt · openwrt 2024-05-06 medium5.3 CVE-2023-32871 In DA, there is a possible permission bypass due to an incorrect status check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2024-05-06 medium6.6 CVE-2024-20054 In gnss, there is a possible escalation of privilege due to a missing bounds check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2024-04-01 medium4.4 CVE-2024-20052 In flashc, there is a possible information disclosure due to an uncaught exception. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2024-04-01 medium4.4 CVE-2024-20050 In flashc, there is a possible information disclosure due to an uncaught exception. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2024-04-01 medium4.4 CVE-2024-20049 In flashc, there is a possible information disclosure due to an uncaught exception. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2024-04-01 medium6.7 CVE-2024-20023 In flashc, there is a possible out of bounds write due to lack of valudation. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2024-03-04 medium6.7 CVE-2024-20022 In lk, there is a possible escalation of privilege due to a missing bounds check. linuxfoundation · yocto, rdkcentral · rdkb, google · android +1 2024-03-04 medium6.7 CVE-2024-20006 In da, there is a possible out of bounds write due to a missing bounds check. rdkcentral · rdk-b, google · android, openwrt · openwrt 2024-02-05 medium6.7 CVE-2023-32855 In aee, there is a possible escalation of privilege due to a missing permission check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2023-12-04 medium6.7 CVE-2023-20832 In gps, there is a possible out of bounds write due to a missing bounds check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2023-09-04 medium6.7 CVE-2023-20831 In gps, there is a possible out of bounds write due to a missing bounds check. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2023-09-04

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.