NetSight

Security Dashboard

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

Reset
604 matching advisories · page 4 of 21Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2026-97579 In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: bound AV1 tile-start copy to the array capacity vdec_av1_slice_set… 57 days ago unscored CVE-2026-97501 In the Linux kernel, the following vulnerability has been resolved: pinctrl: mediatek: paris: bypass pinctrl GPIO layer in set GPIO direction pinctrl_gpio_dire… 58 days ago unscored CVE-2026-97414 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8365-afe-pcm: fix possible NULL-pointer dereferences in mt8365_afe_suspen… 58 days ago unscored CVE-2026-93819 In the Linux kernel, the following vulnerability has been resolved: PCI: mediatek: Protect root bus removal with rescan lock Hold the pci_rescan_remove_lock lo… 58 days ago unscored CVE-2026-92482 In the Linux kernel, the following vulnerability has been resolved: pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip The gpio_chip is allocated wi… 2026-09-17 unscored CVE-2026-92481 In the Linux kernel, the following vulnerability has been resolved: pinctrl: mediatek: free EINT resources on unbind mtk_eint_do_init() creates an IRQ domain, … 2026-09-17 unscored CVE-2026-90422 In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: pllfh: Fix IO remapping leak in register_pllfhs error path When mtk_clk_regi… 2026-09-17 medium5.3 CVE-2026-20504 In Modem, there is a possible system crash due to a missing bounds check. mediatek · mt2735_firmware, mediatek · mt6833_firmware, mediatek · mt6853_firmware +9 2026-09-07 medium5.3 CVE-2026-20503 In Modem, there is a possible system crash due to a missing bounds check. mediatek · mt2716_firmware, mediatek · mt2735_firmware, mediatek · mt2737_firmware +9 2026-09-07 high8.4 CVE-2026-20502 In vdec, there is a possible out of bounds write due to a missing bounds check. mediatek · mt2718_firmware, mediatek · mt6580_firmware, mediatek · mt6739_firmware +9 2026-09-07 high8.4 CVE-2026-20501 In vdec, there is a possible out of bounds write due to a heap buffer overflow. mediatek · mt2718_firmware, mediatek · mt6580_firmware, mediatek · mt6739_firmware +9 2026-09-07 medium4.2 CVE-2026-20518 In geniezone, there is a possible information disclosure due to a missing bounds check. MediaTek, Inc. · MediaTek chipset 2026-09-07 medium5.0 CVE-2026-20515 In gpu, there is a possible system crash due to use after free. MediaTek, Inc. · MediaTek chipset 2026-09-07 medium5.0 CVE-2026-20500 In Modem, there is a possible system crash due to improper input validation. mediatek · mt2716_firmware, mediatek · mt6835_firmware, mediatek · mt6858_firmware +10 2026-09-07 high7.8 CVE-2026-80751 In the Linux kernel, the following vulnerability has been resolved: pmdomain: mediatek: mfg: initialize prev_o in mtk_mfg_attach_dev() mtk_mfg_attach_dev() rea… 2026-09-03 high8.4 CVE-2026-80750 In the Linux kernel, the following vulnerability has been resolved: pmdomain: mediatek: fix remaining %pOF after of_node_put() scpsys_get_bus_protection_legacy… 2026-09-03 unscored CVE-2026-72260 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8192: Check runtime resume during probe The MT8192 AFE probe enables runt… 2026-08-15 unscored CVE-2026-72259 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8192: Release reserved memory on cleanup The MT8192 AFE probe calls of_re… 2026-08-15 unscored CVE-2026-72258 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8183: Release reserved memory on cleanup The MT8183 AFE probe can assign … 2026-08-15 unscored CVE-2026-72008 In the Linux kernel, the following vulnerability has been resolved: pmdomain: mediatek: Fix possible nullptr KP in HWV cleanup/on-check Should probe fail for H… 2026-08-15 medium6.0 CVE-2026-20498 In geniezone, there is a possible escalation of privilege due to a missing permission check. mediatek · mt6991_firmware, mediatek · mt8768_firmware, mediatek · mt8791t_firmware +7 2026-08-03 medium6.0 CVE-2026-20497 In geniezone, there is a possible out of bounds write due to a missing bounds check. mediatek · mt6989_firmware, mediatek · mt8755_firmware, mediatek · mt8768_firmware +8 2026-08-03 medium4.4 CVE-2026-20496 In geniezone, there is a possible out of bounds read due to a missing bounds check. mediatek · mt6983_firmware, mediatek · mt8676_firmware, mediatek · mt8678_firmware +9 2026-08-03 high7.8 CVE-2026-20495 In Bluetooth driver, there is a possible permission bypass due to a missing permission check. mediatek · mt7925_firmware, mediatek · mt7927_firmware, mediatek · mt7902_firmware +3 2026-08-03 medium5.5 CVE-2026-20494 In wifi, there is a possible out of bounds read due to a missing bounds check. mediatek · mt6890_firmware, mediatek · mt6988_firmware, mediatek · mt6990_firmware 2026-08-03 medium4.4 CVE-2026-20493 In wifi, there is a possible out of bounds write due to a missing bounds check. mediatek · mt6890_firmware, mediatek · mt6988_firmware, mediatek · mt6990_firmware 2026-08-03 medium5.5 CVE-2026-20492 In Audio HAL, there is a possible system becoming unresponsive due to a race condition. mediatek · mt6990_firmware, mediatek · mt2735_firmware, mediatek · mt2737_firmware +3 2026-08-03 medium5.5 CVE-2026-20491 In med, there is a possible out of bounds write due to an incorrect bounds check. mediatek · mt2735_firmware, mediatek · mt2737_firmware, mediatek · mt6890_firmware +2 2026-08-03 medium4.4 CVE-2026-20490 In ccci, there is a possible out of bounds read due to a missing bounds check. mediatek · mt6813_firmware, mediatek · mt6982vb_firmware, mediatek · mt6986_firmware +2 2026-08-03 medium4.4 CVE-2026-20489 In display, there is a possible information disclosure due to an integer overflow. mediatek · mt6991_firmware, mediatek · mt6993_firmware, mediatek · mt8126_firmware +9 2026-08-03

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.