VulnerabilityPublished 1 Nov 2026

CVE-2026-120226: Hangzhou Xiongmai Technology P2PAPI.dll · Buffer Overflow

Affects Hangzhou Xiongmai Technology P2PAPI.dllSource CVE Database V5

Compare

Public exploit available · CVSS 4.8 Medium.

Data as of 1 Nov 2026, 12:13 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulDB)	CVSS 4.0	4.8
CNA (VulDB)	CVSS 3.1	3.3
CNA (VulDB)	CVSS 3.0	3.3
CNA (VulDB)	CVSS 2.0	1.7

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Hangzhou Xiongmai TechnologyP2PAPI.dll	Affected =1.3.3.32	Fixed in–

CPE configurations (1)

cpe:2.3:a:hangzhou_xiongmai_technology:p2papi.dll:*:*:*:*:*:*:*:*

AI-suggested

Since exploitation requires local access, restricting local user privileges and limiting access to the vulnerable component may reduce risk. Monitor for vendor advisories for any future patches.

Description

CVE-2026-120226 is a buffer overflow vulnerability in the P2PAPI.dll version 1.3.3.32 from Hangzhou Xiongmai Technology on Windows. It affects the P2PAPI_Connect function of the P2P SDK component. The vulnerability arises from improper handling of string input arguments, leading to a buffer overflow. Exploitation requires local access. Public exploit code has been disclosed. The vendor was contacted but did not respond or provide a fix.

Impact

Successful exploitation could lead to memory corruption via buffer overflow, potentially causing application crashes or other undefined behavior. The attack requires local access and low privileges. There is no indication of remote exploitation or privilege escalation. No vendor fix or mitigation has been provided.

Summary

This vulnerability in Hangzhou Xiongmai Technology's P2PAPI.dll 1.3.3.32 involves a buffer overflow in the P2PAPI_Connect function due to unsafe manipulation of string input arguments. The flaw allows a local attacker with low privileges to potentially cause memory corruption. The vulnerability has a CVSS 4.8 (medium) score and public exploit code is available. The vendor has not issued any advisory or patch.

References

Community reviews

Loading reviews…