NetSight

Security Dashboard

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

Reset
238 matching advisories · page 2 of 8Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-20479 In Modem, there is a possible out of bounds read due to a missing bounds check. mediatek · mt2735_firmware, mediatek · mt6833_firmware, mediatek · mt6853_firmware +9 2026-08-03 high7.8 CVE-2026-46308 In the Linux kernel, the following vulnerability has been resolved: pmdomain: mediatek: fix use-after-free in scpsys_get_bus_protection_legacy() In scpsys_get_… linux · linux_kernel 2026-06-08 high7.8 CVE-2026-21030 Improper access control in MediaTek Audio HAL prior to SMR Jun-2026 Release 1 allows local attackers to trigger privileged functions. samsung · android 2026-06-05 high7.8 CVE-2026-20455 In geniezone, there is a possible out of bounds write due to a missing bounds check. mediatek · mt6739_firmware, mediatek · mt6761_firmware, mediatek · mt6765_firmware +9 2026-06-01 high8.0 CVE-2026-20452 In wlan AP driver, there is a possible memory corruption due to a heap buffer overflow. mediatek · mt6890_firmware, mediatek · mt7615_firmware, mediatek · mt7915_firmware +6 2026-06-01 high7.8 CVE-2026-45909 In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: Drop __initconst from gates Since commit 8ceff24a754a ("clk: mediatek: clk-g… linux · linux_kernel 2026-05-27 high7.8 CVE-2026-31584 In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: fix use-after-free in encoder release path The fops_vcodec_release… linux · linux_kernel 2026-04-24 high8.0 CVE-2026-20432 In Modem, there is a possible out of bounds write due to a missing bounds check. mediatek · mt2735_firmware, mediatek · mt2737_firmware, mediatek · mt6779_firmware +9 2026-04-07 high8.0 CVE-2026-20433 In Modem, there is a possible out of bounds write due to a missing bounds check. mediatek · mt2735_firmware, mediatek · mt2737_firmware, mediatek · mt6813_firmware +10 2026-04-07 high7.5 CVE-2026-20434 In Modem, there is a possible out of bounds write due to a missing bounds check. mediatek · lr12a, mediatek · lr13, mediatek · nr15 +2 2026-03-02 high8.8 CVE-2026-20430 In wlan AP FW, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2026-03-02 high7.8 CVE-2026-20423 In wlan STA driver, there is a possible out of bounds write due to a missing bounds check. mediatek · nbiot_sdk 2026-03-02 high8.8 CVE-2026-20408 In wlan, there is a possible out of bounds write due to a heap buffer overflow. mediatek · software_development_kit, openwrt · openwrt 2026-02-02 high7.5 CVE-2026-20401 In Modem, there is a possible system crash due to an uncaught exception. mediatek · nr15 2026-02-02 high7.8 CVE-2025-71071 In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: fix use-after-free on probe deferral The driver is dropping the references … linux · linux_kernel 2026-01-13 high7.1 CVE-2025-68184 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Disable AFBC support on Mediatek DRM driver Commit c410fa9b07c3 ("drm/mediate… 2025-12-16 high7.1 CVE-2023-53748 In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Fix potential array out-of-bounds in decoder queue_setup variable … 2025-12-08 high8.0 CVE-2025-20742 In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-11-04 high7.8 CVE-2025-20737 In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-11-04 high7.8 CVE-2025-20735 In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-11-04 high7.8 CVE-2025-20733 In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-11-04 high7.8 CVE-2025-20728 In wlan STA driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit 2025-11-04 high8.1 CVE-2025-20727 In Modem, there is a possible out of bounds write due to a heap buffer overflow. mediatek · lr12a, mediatek · nr15, mediatek · nr16 +2 2025-11-04 high7.5 CVE-2025-20725 In ims service, there is a possible out of bounds write due to a missing bounds check. mediatek · lr12a, mediatek · nr15, mediatek · nr16 +1 2025-11-04 high7.5 CVE-2025-20726 In Modem, there is a possible out of bounds write due to an incorrect bounds check. mediatek · lr12a, mediatek · nr15, mediatek · nr16 +3 2025-11-04 high7.8 CVE-2025-20721 In imgsensor, there is a possible out of bounds write due to a missing bounds check. mediatek · iot_yocto, google · android 2025-10-14 high8.8 CVE-2025-20720 In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-10-14 high8.8 CVE-2025-20719 In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-10-14 high7.8 CVE-2025-20718 In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-10-14 high7.8 CVE-2025-20717 In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. mediatek · software_development_kit, openwrt · openwrt 2025-10-14

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.