{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "source": "REFERENCES"
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "69a97b3b39cc218f044f1c8896f4d3d8757bb394"
            }
          ],
          "repo": "https://github.com/nanomq/nanomq",
          "type": "GIT"
        },
        {
          "database_specific": {
            "extracted_events": [
              {
                "introduced": "0"
              },
              {
                "fixed": "0.24.11"
              }
            ],
            "source": [
              "AFFECTED_FIELD",
              "REFERENCES"
            ]
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "522ec62e29e60d1122f2aedaa6e702dcf089f7bb"
            }
          ],
          "repo": "https://github.com/nanomq/nanonng",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-q36f-83mh-pcv2"
  ],
  "database_specific": {
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
      "CWE-476"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/32xxx/CVE-2026-32134.json"
  },
  "details": "NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. In versions 0.24.10 and below, when NanoMQ handles high-concurrency reconnect traffic using a reconnect-collision payload, the broker can crash due to a NULL pointer dereference during MQTT session resumption for clean_start=0 clients. The transport's p_peer callback (tcptran_pipe_peer()) iterates cpipe-\u003esubinfol while copying session metadata from the cached old pipe to the new reconnecting pipe, without checking whether the pointer is NULL. Under a reconnect race, cpipe-\u003esubinfol can be freed and set to NULL before session restore invokes this function, resulting in a remote unauthenticated Denial-of-Service (process crash) condition. This issue has been fixed in version 0.24.11.",
  "id": "CVE-2026-32134",
  "modified": "2026-07-15T01:48:58.760716343Z",
  "published": "2026-05-19T17:22:13.431Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/nanomq/nanomq/releases/tag/0.24.11"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/32xxx/CVE-2026-32134.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/nanomq/nanomq/security/advisories/GHSA-q36f-83mh-pcv2"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32134"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/nanomq/nanomq/issues/2241"
    },
    {
      "type": "FIX",
      "url": "https://github.com/nanomq/NanoNNG/commit/522ec62e29e60d1122f2aedaa6e702dcf089f7bb"
    }
  ],
  "schema_version": "1.8.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "NanoMQ: NULL Pointer Dereference Crash in tcptran_pipe_peer During Session Restore"
}