NetSight

Security Dashboard

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

Reset
167 matching advisories · page 5 of 6Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.4 CVE-2026-5590 A race condition during TCP connection teardown can cause tcp_recv() to operate on a connection that has already been released. zephyrproject · zephyr 2026-04-05 medium6.1 CVE-2026-4179 Issues in stm32 USB device driver (drivers/usb/device/usb_dc_stm32.c) can lead to an infinite while loop. zephyrproject · zephyr 2026-03-16 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 medium4.3 CVE-2025-10457 The function responsible for handling BLE connection responses does not verify whether a response is expected—that is, whether the device has initiated a conne… zephyrproject · zephyr 2025-09-19 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.3 CVE-2024-6444 No proper validation of the length of user input in olcp_ind_handler in zephyr/subsys/bluetooth/services/ots/ots_client.c. zephyrproject · zephyr 2024-10-04 medium6.3 CVE-2024-6443 In utf8_trunc in zephyr/lib/utils/utf8.c, last_byte_p can point to one byte before the string pointer if the string is empty. zephyrproject · zephyr 2024-10-04 medium6.3 CVE-2024-6442 In ascs_cp_rsp_add in /subsys/bluetooth/audio/ascs.c, an unchecked tailroom could lead to a global buffer overflow. zephyrproject · zephyr 2024-10-04 medium6.3 CVE-2024-5931 BT: Unchecked user input in bap_broadcast_assistant zephyrproject · zephyr 2024-09-13 medium6.8 CVE-2024-6258 BT: Missing length checks of net_buf in rfcomm_handle_data zephyrproject · zephyr 2024-09-13 medium6.5 CVE-2024-3332 A malicious BLE device can send a specific order of packet sequence to cause a DoS attack on the victim BLE device zephyrproject · zephyr 2024-07-03 medium6.8 CVE-2024-3077 An malicious BLE device can crash BLE victim device by sending malformed gatt packet zephyrproject · zephyr 2024-03-29 medium4.4 CVE-2023-5779 can: out of bounds in remove_rx_filter function zephyrproject · zephyr 2024-02-18 medium4.4 CVE-2023-5139 Potential buffer overflow vulnerability at the following location in the Zephyr STM32 Crypto driver zephyrproject · zephyr 2023-10-26 medium6.3 CVE-2023-5753 Potential buffer overflows in the Bluetooth subsystem due to asserts being disabled in /subsys/bluetooth/host/hci_core.c zephyrproject · zephyr 2023-10-25 medium6.3 CVE-2023-4260 Potential off-by-one buffer overflow vulnerability in the Zephyr fuse file system. zephyrproject · zephyr 2023-09-27 medium6.4 CVE-2023-4265 Potential buffer overflow vulnerabilities in the following locations: https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/usb/device/usb_dc_native_p… zephyrproject · zephyr 2023-08-12 medium6.8 CVE-2023-2234 Union variant confusion allows any malicious BT controller to execute arbitrary code on the Zephyr host. zephyrproject · zephyr 2023-07-10 medium5.9 CVE-2023-1902 The bluetooth HCI host layer logic not clearing a global reference to a state pointer after handling connection events may allow a malicious HCI Controller to … zephyrproject · zephyr 2023-07-10 medium5.9 CVE-2023-1901 The bluetooth HCI host layer logic not clearing a global reference to a semaphore after synchronously sending HCI commands may allow a malicious HCI Controller… zephyrproject · zephyr 2023-07-10 medium5.9 CVE-2023-0359 A missing nullptr-check in handle_ra_input can cause a nullptr-deref. zephyrproject · zephyr 2023-07-10 medium6.7 CVE-2023-0779 At the most basic level, an invalid pointer can be input that crashes the device, but with more knowledge of the device’s memory layout, further exploitation i… zephyrproject · zephyr 2023-05-30 medium6.8 CVE-2023-0396 A malicious / defective bluetooth controller can cause buffer overreads in the most functions that process HCI command responses. zephyrproject · zephyr 2023-01-25 medium6.5 CVE-2022-0553 There is no check to see if slot 0 is being uploaded from the device to the host. zephyrproject · zephyr 2023-01-11 medium4.0 CVE-2021-3435 Information leakage in le_ecred_conn_req(). zephyrproject · zephyr 2022-06-28 medium4.9 CVE-2021-3434 Stack based buffer overflow in le_ecred_conn_req(). zephyrproject · zephyr 2022-06-28 medium4.0 CVE-2021-3433 Invalid channel map in CONNECT_IND results to Deadlock. zephyrproject · zephyr 2022-06-28 medium4.3 CVE-2021-3432 Invalid interval in CONNECT_IND leads to Division by Zero. zephyrproject · zephyr 2022-06-28

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.