NetSight

Security Dashboard

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

Reset
22 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-36590 An issue in EMQ NanoMQ v.0.24.9 allows a remote attacker to cause a denial of service via the nni_qos_db_set function in broker_tcp.c component emqx · nanomq 2026-07-15 high7.7 CVE-2026-33356 In Meari IoT Cloud MQTT Broker deployments running EMQX 4.x, any authenticated low-privilege account can subscribe to global wildcard topics and receive teleme… 2026-05-11 high7.5 CVE-2026-32135 NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. emqx · nanomq 2026-04-20 high7.5 CVE-2026-21888 NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. emqx · nanomq 2026-03-11 high7.5 CVE-2024-48077 NanoMQ v0.22.7 is vulnerable to Denial of Service (DoS) due to improper resource throttling. emqx · nanomq 2026-01-15 high7.5 CVE-2025-59946 NanoMQ MQTT Broker (NanoMQ) is an Edge Messaging Platform. emqx · nanomq 2025-12-27 high8.8 CVE-2024-42655 An access control issue in NanoMQ v0.21.10 allows attackers to bypass security restrictions and access sensitive system topic messages using MQTT wildcard char… emqx · nanomq 2025-07-29 high7.5 CVE-2024-42651 NanoMQ v0.17.9 was discovered to contain a heap use-after-free vulnerability via the component sub_Ctx_handle. emqx · nanomq 2025-07-29 high7.5 CVE-2024-42650 NanoMQ 0.17.5 was discovered to contain a segmentation fault via the component /nanomq/pub_handler.c. emqx · nanomq 2025-07-15 high7.5 CVE-2024-42646 A segmentation fault in NanoMQ v0.21.10 allows attackers to cause a Denial of Service (DoS) via crafted messages. emqx · nanomq 2025-07-14 high7.5 CVE-2024-44460 An invalid read size in Nanomq v0.21.9 allows attackers to cause a Denial of Service (DoS). emqx · nanomq 2024-09-12 high7.5 CVE-2024-31041 Null Pointer Dereference vulnerability in topic_filtern function in mqtt_parser.c in NanoMQ 0.21.7 allows attackers to cause a denial of service. emqx · nanomq 2024-04-17 high7.5 CVE-2023-34494 NanoMQ 0.16.5 is vulnerable to heap-use-after-free in the nano_ctx_send function of nmq_mqtt.c. emqx · nanomq 2023-06-12 high7.8 CVE-2023-34488 NanoMQ 0.17.5 has a one-byte heap-based buffer over-read in the conn_handler function of mqtt_parser.c when it processes malformed messages. emqx · nanomq 2023-06-12 high7.5 CVE-2023-33657 A use-after-free vulnerability exists in NanoMQ 0.17.2. emqx · nanomq 2023-06-08 high7.5 CVE-2023-33660 A heap buffer overflow vulnerability exists in NanoMQ 0.17.2. emqx · nanomq 2023-06-08 high7.5 CVE-2023-33658 A heap buffer overflow vulnerability exists in NanoMQ 0.17.2. emqx · nanomq 2023-06-08 high7.5 CVE-2023-33659 A heap buffer overflow vulnerability exists in NanoMQ 0.17.2. emqx · nanomq 2023-06-06 high7.5 CVE-2023-29996 In NanoMQ v0.15.0-0, segment fault with Null Pointer Dereference occurs in the process of decoding subinfo_decode and unsubinfo_decode. emqx · nanomq 2023-05-04 high7.5 CVE-2023-29995 In NanoMQ v0.15.0-0, a Heap overflow occurs in copyn_utf8_str function of mqtt_parser.c emqx · nanomq 2023-05-04 high7.5 CVE-2023-29994 In NanoMQ v0.15.0-0, Heap overflow occurs in read_byte function of mqtt_code.c. emqx · nanomq 2023-05-04 high7.5 CVE-2021-33175 EMQ X Broker versions prior to 4.2.8 are vulnerable to a denial of service attack as a result of excessive memory consumption due to the handling of untrusted … emqx · emq_x_broker 2021-06-08

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.