NetSight

Security Dashboard

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

Reset
124 matching advisories · page 3 of 5Index updated 6 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-8023 Zephyr's HTTP server (subsys/net/lib/http) provides a static-filesystem resource type (HTTP_RESOURCE_TYPE_STATIC_FS, available when CONFIG_FILE_SYSTEM is enabl… zephyrproject · zephyr 2026-06-29 high8.1 CVE-2026-7656 The IPv6 Neighbor Discovery handlers in subsys/net/ip/ipv6_nbr.c (handle_ra_input, handle_ns_input, handle_na_input) used an incorrect boolean expression that … zephyrproject · zephyr 2026-06-29 high7.4 CVE-2026-10646 Zephyr's BSD-sockets getaddrinfo() implementation (subsys/net/lib/sockets/getaddrinfo.c) passes a pointer to a stack-allocated state object (struct getaddrinfo… zephyrproject · zephyr 2026-06-28 high8.7 CVE-2026-10643 Zephyr's IP socket recvmsg() implementation (subsys/net/lib/sockets/sockets_inet.c, insert_pktinfo()) validated the user-supplied ancillary (msg_control) buffe… zephyrproject · zephyr 2026-06-27 high7.5 CVE-2026-13351 Zephyr's IPv6 network stack can be prevented from receiving or processing future incoming packets by sending a small number of maliciously fragmented IPv6 pack… zephyrproject · zephyr 2026-06-25 high7.1 CVE-2026-10658 bt_iso_recv() in subsys/bluetooth/host/iso.c pulled the ISO SDU header (4 bytes) or, when the timestamp flag is set, the timestamped SDU header (8 bytes) from … zephyrproject · zephyr 2026-06-22 high7.1 CVE-2026-10651 bt_sdp_parse_attribute() in subsys/bluetooth/host/classic/sdp.c validated only that the SDP record buffer held the type-marker byte plus the 2-byte attribute I… zephyrproject · zephyr 2026-06-22 high7.1 CVE-2026-10641 Zephyr's Bluetooth Classic Hands-Free Profile (HFP) Hands-Free role parser (subsys/bluetooth/host/classic/hfp_hf.c) contains an out-of-bounds write. zephyrproject · zephyr 2026-06-17 high7.6 CVE-2026-5068 A remote, unauthenticated BLE peer can trigger a 2-byte out-of-bounds write in the Bluetooth host during L2CAP LE CoC SDU reassembly. zephyrproject · zephyr 2026-06-09 high7.3 CVE-2026-1679 The eswifi socket offload driver copies user-provided payloads into a fixed buffer without checking available space; oversized sends overflow `eswifi->buf`, co… zephyrproject · zephyr 2026-03-28 high7.6 CVE-2025-7403 Unsafe handling in bt_conn_tx_processor causes a use-after-free, resulting in a write-before-zero. zephyrproject · zephyr 2025-09-19 high7.6 CVE-2025-10458 Parameters are not validated or sanitized, and are later used in various internal operations. zephyrproject · zephyr 2025-09-19 high7.1 CVE-2025-10456 A vulnerability was identified in the handling of Bluetooth Low Energy (BLE) fixed channels (such as SMP or ATT). zephyrproject · zephyr 2025-09-19 high7.5 CVE-2025-2962 A denial-of-service issue in the dns implemenation could cause an infinite loop. zephyrproject · zephyr 2025-06-24 high8.2 CVE-2025-1675 The function dns_copy_qname in dns_pack.c performs performs a memcpy operation with an untrusted field and does not check if the source buffer is large enough … zephyrproject · zephyr 2025-02-25 high8.2 CVE-2025-1674 A lack of input validation allows for out of bounds reads caused by malicious or malformed packets. zephyrproject · zephyr 2025-02-25 high8.2 CVE-2025-1673 A malicious or malformed DNS packet without a payload can cause an out-of-bounds read, resulting in a crash (denial of service) or an incorrect computation. zephyrproject · zephyr 2025-02-25 high8.6 CVE-2024-10395 No proper validation of the length of user input in http_server_get_content_type_from_extension. zephyrproject · zephyr 2025-02-03 high7.5 CVE-2024-8798 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-12-16 high7.6 CVE-2024-6259 BT: HCI: adv_ext_report Improper discarding in adv_ext_report zephyrproject · zephyr 2024-09-13 high7.6 CVE-2024-6137 BT: Classic: SDP OOB access in get_att_search_list zephyrproject · zephyr 2024-09-13 high7.6 CVE-2024-6135 BT:Classic: Multiple missing buf length checks zephyrproject · zephyr 2024-09-13 high8.2 CVE-2024-5754 BT: Encryption procedure host vulnerability zephyrproject · zephyr 2024-09-13 high7.6 CVE-2024-4785 BT: Missing Check in LL_CONNECTION_UPDATE_IND Packet Leads to Division by Zero zephyrproject · zephyr 2024-08-19 high8.6 CVE-2023-7060 Zephyr OS IP packet handling does not properly drop IP packets arriving on an external interface with a source address equal to 127.0.01 or the destination add… zephyrproject · zephyr 2024-03-15 high7.3 CVE-2023-6881 Possible buffer overflow in is_mount_point zephyrproject · zephyr 2024-02-29 high8.2 CVE-2024-1638 The documentation specifies that the BT_GATT_PERM_READ_LESC and BT_GATT_PERM_WRITE_LESC defines for a Bluetooth characteristic: Attribute read/write permission… zephyrproject · zephyr 2024-02-19 high8.0 CVE-2023-6249 Signed to unsigned conversion esp32_ipm_send zephyrproject · zephyr 2024-02-18 high8.0 CVE-2023-6749 Unchecked length coming from user input in settings shell zephyrproject · zephyr 2024-02-18 high8.3 CVE-2023-5055 Possible variant of CVE-2021-3434 in function le_ecred_reconf_req. zephyrproject · zephyr 2023-11-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.