CVE-2026-111732: Out-of-bounds write when parsing AR Vendor Block requests
P-Net before 1.0.3, when built with PNETOPTIONARVENDORBLOCKS enabled, parses a data length from a field of the ARVendorBlock request that is not part of the block definition and uses it as the number of bytes to copy into a fixed-size buffer, without comparing it with the buffer size or the block length. A crafted Connect request causes an out-of-bounds write. This can lead to a crash (denial of service) or potentially arbitrary code execution.
This option is disabled by default.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
P-Netto a version that resolves this vulnerability.Fixed in 1.0.3
Event History
Frequently Asked Questions
Which deployments are affected?
Only P-Net versions before 1.0.3 built with PNET_OPTION_AR_VENDOR_BLOCKS enabled are affected. The option is disabled by default, so default builds are not affected.
What does an attacker need to exploit this issue?
An attacker needs to send a crafted Connect request containing an ARVendorBlock request. No authentication or user interaction is indicated by the provided CVSS vector.
What can be done if upgrading is not immediately possible?
Build or deploy P-Net without PNET_OPTION_AR_VENDOR_BLOCKS enabled. This removes the affected AR Vendor Block parsing path described in the vulnerability.
How can I determine whether my deployment is vulnerable?
Check whether the deployed P-Net version is earlier than 1.0.3 and whether it was built with PNET_OPTION_AR_VENDOR_BLOCKS enabled. Systems meeting both conditions are affected.