CVE-2025-65953
BaseFortify
Publication date: 2025-11-25
Last updated on: 2025-11-25
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| nanomq | nanomq | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Heap-Use-After-Free (UAF) issue in the TCP transport component of the NanoMQ MQTT Broker prior to version 0.22.5. It occurs due to improper resource management and premature cleanup of message and pipe structures when handling specific malformed MQTT version 5 retain message traffic. This can lead to the use of memory after it has been freed, potentially causing crashes or other unintended behavior.
How can this vulnerability impact me? :
The vulnerability can lead to instability or crashes in the NanoMQ MQTT Broker due to use of freed memory. This may result in denial of service or potentially allow an attacker to execute arbitrary code or cause unexpected behavior by sending malformed MQTT retain messages.
What immediate steps should I take to mitigate this vulnerability?
Upgrade NanoMQ to version 0.22.5 or later, as this version contains the patch that fixes the Heap-Use-After-Free vulnerability in the TCP transport component.