Hangzhou Xiongmai Technology P2PAPI.dll 1.3.3.32 on Windows P2P SDK P2PAPI_Connect input buffer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.40 |
Summary
A vulnerability identified as problematic has been detected in Hangzhou Xiongmai Technology P2PAPI.dll 1.3.3.32 on Windows. This affects the function P2PAPI_Connect of the component P2P SDK. Performing a manipulation of the argument input as part of String results in buffer overflow.
This vulnerability is known as CVE-2026-120226. Attacking locally is a requirement. Furthermore, an exploit is available.
It is advisable to use the suggested workaround.
The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability was found in Hangzhou Xiongmai Technology P2PAPI.dll 1.3.3.32 on Windows (Video Surveillance Software). It has been classified as problematic. This affects the function P2PAPI_Connect of the component P2P SDK. The manipulation of the argument input as part of a String leads to a buffer overflow vulnerability. CWE is classifying the issue as CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. This is going to have an impact on availability.
The bug was discovered 10/04/2026. The weakness was published by Ishan Oshada (Ishan) as confirmed vulnerability report (GitHub Gist). The advisory is shared at gist.github.com. This vulnerability is uniquely identified as CVE-2026-120226. The exploitability is told to be easy. An attack has to be approached locally. Technical details and a public exploit are known.
A public exploit has been developed by Ishan Oshada (Ishan) in Go. The exploit is shared for download at gist.github.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around . The vendor was contacted early about this disclosure but did not respond in any way.
The best possible mitigation is suggested to be Workaround. The vendor did not provide an official patch. As an interim mitigation, callers of P2PAPI_Connect should enforce a maximum length on the VSTD-prefixed string argument (especially the second string argument) before passing it to the SDK. Bound each field to the destination buffer size (A ≤ 63 bytes, B ≤ 63 bytes, C ≤ 63 bytes for FUN_10007fd0). Long-term fix requires the vendor to replace the unbounded strcpy-style loops in FUN_10007fd0, FUN_1000b500, and FUN_10004ef0 with strncpy_s / bounded sscanf conversions, and to enable /guard:cf (CFG is currently disabled).
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.1
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
Researcher Base Score: 5.5
Researcher Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Researcher Base Score: 🔒
Exploiting
Class: Buffer overflowCWE: CWE-120 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Author: Ishan Oshada (Ishan)
Programming Language: 🔒
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: WorkaroundStatus: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Workaround: Avoid calling P2PAPI_Connect with untrusted VSTD-prefixed input. Validate input length at the call boundary before dispatching to any constructor.
Timeline
10/04/2026 Vulnerability found10/05/2026 Vendor informed
10/05/2026 Exploit disclosed
10/05/2026 Countermeasure disclosed
10/31/2026 Advisory disclosed
10/31/2026 VulDB entry created
11/01/2026 VulDB entry last update
Sources
Advisory: gist.github.comResearcher: Ishan Oshada (Ishan)
Status: Confirmed
CNA: VulDB
CVE: CVE-2026-120226 (🔒)
GCVE (CVE): GCVE-0-2026-120226
GCVE (VulDB): GCVE-100-429585
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/31/2026 20:28Updated: 11/01/2026 08:35
Changes: 10/31/2026 20:28 (57), 11/01/2026 08:32 (40), 11/01/2026 08:35 (7)
Complete: 🔍
Submitter: ishanoshada
Committer: ishanoshada
Cache ID: 216::103
Submit
Accepted
- Submit #1013929: Hangzhou Xiongmai Technology Co., Ltd P2PAPI.dll 1.3.3.32 CWE-120: Buffer Copy without Checking Size of Input (by ishanoshada)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.