CVE-2026-44640Disclosure

LOWCVSS 4.5 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD 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.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-843

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

STABLE

Threat summary

  • 2 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Technical details provided in 2 signals
  • Disclosure: 2 classified signals
  • Peaked 1d ago at 1 mentions (2026-05-29); latest day: 1
  • 2 total mentions across 2 days

Deep dive

Activity timeline2 mentions / 2d
00111Mentions · 2026-05-29: 1Mentions · 2026-05-30: 1Technical Details · 2026-05-29: 1Technical Details · 2026-05-30: 105-2905-30
Signal classification1 categories
Disclosure
2100.0%
Referenced assets2 URLs
Full discourse2 posts
  • Vulmon Vulnerability Feed@VulmonFeeds
    Disclosure

    CVE-2026-44640 Type Confusion Vulnerability in NanoMQ MQTT Broker Prior to 0.24.14 https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-44640

    Post summary

    The content announces the discovery of a type confusion vulnerability in NanoMQ MQTT Broker versions before 0.24.14, providing basic technical details but no exploitation or remediation information.

    0000048
    4.0K followersView on X
  • CVE@CVEnew
    Disclosure

    CVE-2026-44640 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… https://www.cve.org/CVERecord?id=CVE-2026-44640

    Post summary

    The text briefly discloses a mismatch bug in NanoMQ prior to version 0.24.14, indicating how connection data is stored and read incorrectly.

    00000128
    57.5K followersView on X

Explore more