Service hang via QUIC dialer type confusion
Published May 29, 2026 · Updated May 29, 2026
Type confusion in NanoMQ before 0.24.14 allows local users to hang the broker by closing a QUIC dialer during connection setup. The nni_quic_dialer_close path reads aio->prov_data as an ex_quic_conn pointer even though dialing stored an nni_quic_conn pointer there. Triggering requires local execution and a pending dial AIO; the demonstrated result is a broker hang, while a crash depends on memory layout and timing.
Summary
What happened
Type confusion in NanoMQ before 0.24.14 allows local users to hang the broker by closing a QUIC dialer during connection setup. The nni_quic_dialer_close path reads aio->prov_data as an ex_quic_conn pointer even though dialing stored an nni_quic_conn pointer there. Triggering requires local execution and a pending dial AIO; the demonstrated result is a broker hang, while a crash depends on memory layout and timing.
The record
- CVE
- CVE-2026-44640
- Published
- May 29, 2026
- Updated
- May 29, 2026
- Vendor
- EMQ Technologies
- Product
- NanoMQ
- Classifications
- CWE-843, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 29, 2026CVE publishedPublication date reported by the CVE source.
- May 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.24.14
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-9fgw-v323-jmjj project-level reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo