CVE-2026-22040

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2026-22040
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-22040.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-22040
Aliases
  • GHSA-v57q-w88m-424r
Published
2026-03-04T21:55:11.238Z
Modified
2026-07-15T01:49:00.535606886Z
Severity
  • 5.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H CVSS Calculator
Summary
NanoMQ 0.24.6 Use-After-Free Leading to Heap Corruption and Broker Crash
Details

NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. In version 0.24.6, by generating a combined traffic pattern of high-frequency publishes and rapid reconnect/kick-out using the same ClientID and massive subscribe/unsubscribe jitter, it is possible to reliably trigger heap memory corruption in the Broker process, causing it to exit immediately with SIGABRT due to free(): invalid pointer. As of time of publication, no known patched versions are available.

Database specific 
{
    "cwe_ids": [
        "CWE-416"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/22xxx/CVE-2026-22040.json",
    "cna_assigner": "GitHub_M"
}
References

Affected packages

Git / github.com/nanomq/nanomq

Affected ranges

Type
GIT
Repo
https://github.com/nanomq/nanomq
Events
Introduced
dc3a3136cd82d5c005b8cd26a65fe53beaaf0eb9
Fixed
dc3a3136cd82d5c005b8cd26a65fe53beaaf0eb9
Database specific 
{
    "cpe": "cpe:2.3:a:emqx:nanomq:*:*:*:*:*:*:*:*",
    "extracted_events": [
        {
            "introduced": "= 0.24.6"
        },
        {
            "last_affected": "= 0.24.6"
        },
        {
            "introduced": "0"
        },
        {
            "fixed": "0.24.6"
        }
    ],
    "source": [
        "AFFECTED_FIELD",
        "CPE_RANGE"
    ]
}

Affected versions

= 0.*
= 0.24.6

Database specific

source 
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-22040.json"