CVE-2026-24822
Heap-Based Buffer Overflow in wxhelper Module of mongoose.C
Publication date: 2026-01-27
Last updated on: 2026-01-27
Assigner: Government Technology Agency of Singapore Cyber Security Group (GovTech CSG)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ttttupup | wxhelper | to 3.9.10.19 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-122 | A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). |
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a heap-based buffer overflow caused by an out-of-bounds write in the wxhelper project's src modules, specifically in the mongoose.C file. It relates to improper handling of the MQTT variable length header, which could allow an attacker to write data beyond the allocated buffer, potentially leading to crashes or arbitrary code execution. [1]
How can this vulnerability impact me? :
The vulnerability can lead to severe security impacts including remote code execution, denial of service, or system compromise because it allows an attacker to exploit the heap-based buffer overflow by sending specially crafted MQTT packets. The CVSS score of 10.0 indicates it is critical and exploitable remotely without authentication. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should apply the security patch that fixes the improper handling of the MQTT variable length header in the wxhelper project. This patch was merged in pull request #515 on April 23, 2025, and addresses the issue in the src/mongoose.c file. Updating wxhelper to a version that includes this patch or manually applying the patch will eliminate the vulnerability. [1]