NetSight

Security Dashboard

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

Reset
19 matching advisories · page 1 of 1Index is being built · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2026-126495 MQTTX desktop through 1.13.3 contains a stored cross-site scripting vulnerability that allows attackers to inject script by publishing malicious MQTT topic nam… emqx · MQTTX 11 days ago medium6.1 CVE-2026-123203 NEURON (CoreNEURON) through 9.0.2 contains a stack buffer overflow vulnerability that allows attackers to corrupt stack memory by supplying over-long tokens in… neuronsimulator · NEURON, emqx · neuron 16 days ago medium6.6 CVE-2026-44725 EMQX is a scalable and reliable MQTT broker for AI, IoT, IIoT, and connected vehicles. 2026-08-20 medium4.3 CVE-2026-6564 A vulnerability was found in EMQ EMQX Enterprise up to 6.1.0. EMQ EMQX Enterprise 2026-04-19 medium4.9 CVE-2026-34608 NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. emqx · nanomq 2026-04-02 medium5.7 CVE-2026-30867 CocoaMQTT: Denial of Service via Reachable Assertion in `PUBLISH` Packet Parsing swift · CocoaMQTT 2026-04-02 medium6.5 CVE-2026-25627 NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. emqx · nanomq 2026-03-30 medium5.3 CVE-2026-22040 NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. emqx · nanomq 2026-03-04 medium6.5 CVE-2025-68699 NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. emqx · nanomq 2026-02-04 medium4.9 CVE-2025-66023 NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. emqx · nanomq 2026-01-01 medium6.5 CVE-2024-42649 NanoMQ v0.22.10 was discovered to contain a memory leak which allows attackers to cause a Denial of Service (DoS) via a crafted PUBLISH message. emqx · nanomq 2025-07-14 medium6.5 CVE-2024-42648 NanoMQ v0.22.10 was discovered to contain a heap overflow which allows attackers to cause a Denial of Service (DoS) via a crafted CONNECT message. emqx · nanomq 2025-07-14 medium4.3 CVE-2024-10965 A vulnerability classified as problematic was found in emqx neuron up to 2.10.0. emqx · neuron 2024-11-07 medium6.3 CVE-2024-10964 A vulnerability classified as critical has been found in emqx neuron up to 2.10.0. emqx · neuron 2024-11-07 medium6.8 CVE-2024-31036 A heap-buffer-overflow vulnerability in the read_byte function in NanoMQ v.0.21.7 allows attackers to cause a denial of service via transmission of crafted hex… emqx · nanomq 2024-04-22 medium6.5 CVE-2024-25767 nanomq 0.21.2 contains a Use-After-Free vulnerability in /nanomq/nng/src/core/socket.c. emqx · nanomq 2024-02-26 medium6.5 CVE-2023-37781 An issue in the emqx_sn plugin of EMQX v4.3.8 allows attackers to execute a directory traversal via uploading a crafted .txt file. emqx · emqx 2023-07-17 medium5.5 CVE-2023-33656 A memory leak vulnerability exists in NanoMQ 0.17.2. emqx · nanomq 2023-05-30 medium5.3 CVE-2021-46434 EMQ X Dashboard V3.0.0 is affected by username enumeration in the "/api /v3/auth" interface. emqx · emqx 2022-03-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.