Skip to main content
VulnerabilityPublished

CVE-2026-111732: RT-Labs P-Net · Out-of-bounds Write

Affects RT-Labs P-NetSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 1.0.3 as a priority.

Data as of 29 Oct 2026, 16:53 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (rt-labs)CVSS 4.09.3
Patch
Available – fixed in 1.0.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade RT-Labs P-Net to 1.0.3.

Affected software

ProductAffectedFixed in
RT-LabsP-NetAffected
  • <1.0.3
Fixed in
  • 1.0.3

AI-suggested

Upgrade RT-Labs P-Net to version 1.0.3 or later, where this vulnerability is fixed. Note that the vulnerable code path requires the PNET_OPTION_AR_VENDOR_BLOCKS option to be enabled, which is disabled by default. If this option is not enabled, the vulnerability is not exploitable. No other mitigations are specified.

Description

CVE-2026-111732 is a critical out-of-bounds write vulnerability in RT-Labs P-Net versions before 1.0.3 when built with the PNET_OPTION_AR_VENDOR_BLOCKS option enabled. The vulnerability arises because the software parses a data length from a field in the ARVendorBlock request that is not defined as part of the block and uses this length to copy data into a fixed-size buffer without proper bounds checking. This can be triggered by a crafted Connect request, potentially causing a crash or arbitrary code execution. The vulnerable option is disabled by default.

References

Community reviews

Loading reviews…