Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 02 Apr 2026 15:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Emqx
Emqx nanomq |
|
| CPEs | cpe:2.3:a:emqx:nanomq:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Emqx
Emqx nanomq |
Wed, 01 Apr 2026 02:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nanomq
Nanomq nanomq |
|
| Vendors & Products |
Nanomq
Nanomq nanomq |
Tue, 31 Mar 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 31 Mar 2026 03:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. Prior to version 0.24.8, NanoMQ’s MQTT-over-WebSocket transport can be crashed by sending an MQTT packet with a deliberately large Remaining Length in the fixed header while providing a much shorter actual payload. The code path copies Remaining Length bytes without verifying that the current receive buffer contains that many bytes, resulting in an out-of-bounds read (ASAN reports OOB / crash). This is remotely triggerable over the WebSocket listener. This issue has been patched in version 0.24.8. | |
| Title | nanomq: OOB Read / Crash (DoS) via Malformed MQTT Remaining Length over WebSocket | |
| Weaknesses | CWE-125 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-31T19:09:34.784Z
Reserved: 2026-02-04T05:15:41.789Z
Link: CVE-2026-25627
Updated: 2026-03-31T19:07:04.865Z
Status : Analyzed
Published: 2026-03-30T21:17:07.750
Modified: 2026-04-02T15:33:55.340
Link: CVE-2026-25627
No data.
OpenCVE Enrichment
Updated: 2026-04-02T20:22:50Z