CVE-2024-44460: Nanomq · Out-of-bounds Read
Affects NanomqSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubzzh-newlearner/Nanomqpkg:github/zzh-newlearner/NanomqOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official patch is released, organizations should implement network-level protections such as firewall rules to restrict access to Nanomq services to trusted hosts only. Deploying intrusion detection or prevention systems (IDS/IPS) with anomaly detection capabilities can help identify and block suspicious traffic patterns targeting Nanomq. Network segmentation should isolate Nanomq servers from untrusted networks to reduce exposure. Monitoring Nanomq logs and system stability can provide early warning signs of exploitation attempts. Organizations should also engage with the Nanomq vendor or open-source community to track patch releases and apply updates promptly. In environments where high availability is critical, consider deploying redundant messaging brokers or failover mechanisms to minimize service disruption. Additionally, conducting regular security assessments and penetration tests focusing on messaging infrastructure can help identify and remediate related vulnerabilities proactively.
Description
An invalid read size in Nanomq v0.21.9 allows attackers to cause a Denial of Service (DoS).