NetSight

Security Dashboard

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

Reset
17 matching advisories · page 1 of 1Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.1 CVE-2026-82391 The HTTP/2 front-end of the Zephyr HTTP server aliased connection receive state as a scratch output. zephyrproject · zephyr, zephyrproject-rtos · Zephyr 11 days ago critical9.8 CVE-2026-13214 The OCPP 1.6 client in subsys/net/lib/ocpp/ocpp_j.c contains a stack buffer overflow in parse_getconfig_msg(). zephyrproject · zephyr 2026-08-25 critical9.8 CVE-2026-5067 A remote, unauthenticated attacker can trigger memory corruption in Zephyr's HTTP server WebSocket upgrade path by sending a crafted Sec-WebSocket-Key header. zephyrproject · zephyr 2026-06-09 critical9.4 CVE-2026-1678 dns_unpack_name() caches the buffer tailroom once and reuses it while appending DNS labels. zephyrproject · zephyr 2026-03-05 critical9.3 CVE-2024-11263 When the Global Pointer (GP) relative addressing is enabled (CONFIG_RISCV_GP=y), the gp reg points at 0x800 bytes past the start of the .sdata section which is… zephyrproject · zephyr 2024-11-15 critical9.6 CVE-2021-3329 Lack of proper validation in HCI Host stack initialization can cause a crash of the bluetooth stack zephyrproject · zephyr 2023-02-26 critical9.8 CVE-2022-3806 Inconsistent handling of error cases in bluetooth hci may lead to a double free condition of a network buffer. zephyrproject · zephyr 2023-01-25 critical9.6 CVE-2023-0397 A malicious / defect bluetooth controller can cause a Denial of Service due to unchecked input in le_read_buffer_size_complete. zephyrproject · zephyr 2023-01-19 critical9.6 CVE-2021-3966 usb device bluetooth class includes a buffer overflow related to implementation of net_buf_add_mem. zephyrproject · zephyr 2023-01-11 critical9.6 CVE-2021-3625 Buffer overflow in Zephyr USB DFU DNLOAD. zephyrproject · zephyr 2021-10-05 critical9.0 CVE-2020-13601 Possible read out of bounds in dns read. zephyrproject · zephyr 2021-05-25 critical9.0 CVE-2020-10071 The Zephyr MQTT parsing code performs insufficient checking of the length field on publish messages, allowing a buffer overflow and potentially remote code exe… zephyrproject · zephyr 2020-06-05 critical9.0 CVE-2020-10070 In the Zephyr Project MQTT code, improper bounds checking can result in memory corruption and possibly remote code execution. zephyrproject · zephyr 2020-06-05 critical9.0 CVE-2020-10062 An off-by-one error in the Zephyr project MQTT packet length decoder can result in memory corruption and possible remote code execution. zephyrproject · zephyr 2020-06-05 critical9.0 CVE-2020-10022 A malformed JSON payload that is received from an UpdateHub server may trigger memory corruption in the Zephyr OS. zephyrproject · zephyr 2020-05-11 critical9.8 CVE-2017-14199 A buffer overflow has been found in the Zephyr Project's getaddrinfo() implementation in 1.9.0 and 1.10.0. zephyrproject · zephyr 2019-04-12 critical9.8 CVE-2018-1000800 zephyr-rtos version 1.12.0 contains a NULL base pointer reference vulnerability in sys_ring_buf_put(), sys_ring_buf_get() that can result in CPU Page Fault (er… zephyrproject · zephyr 2018-09-06

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.