# CVE-2026-111731: P-Net infinite loop in PDPortDataCheck record handling

Source: https://junglewise.ai/threats/cve-2026-111731-p-net-before-1-0-3-enters-an-infinite-loop-when-handling-a-read  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-29. Updated: 2026-10-29  
License: CC BY 4.0 with a link back

CVE-2026-111731 · Severity: info · Published 2026-10-29

P-Net is a protocol implementation library used in industrial and network devices. A flaw in how it processes certain network requests causes the device to enter an infinite loop and stop responding entirely, allowing remote attackers to cause a denial of service without authentication.

Technologies: [RT-Labs P-Net](https://junglewise.ai/threats/technologies/p-net). Vendors: [RT-Labs](https://junglewise.ai/threats/vendors/rt-labs).

## Quick answers

**Is CVE-2026-111731 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-111731 being exploited in the wild.

**How severe is CVE-2026-111731?** Informational severity, published 29 October 2026.

**Which products and versions are affected?** RT-Labs P-Net before 1.0.3.

**Is there a fix for CVE-2026-111731?** Yes: fixed in P-Net 1.0.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-111731 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-111731?** Check whether you run RT-Labs P-Net at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in P-Net 1.0.3

## Technical details

The vulnerability is an infinite loop triggered by a read request for the PDPortDataCheck record with subslot 0 (whole module). The port iteration logic fails to advance to the next port during loop processing, causing the request handler to hang indefinitely. A remote unauthenticated attacker on the network can trigger this condition to crash device responsiveness.

## Affected products

- RT Labs P-Net before 1.0.3

## Timeline

- 2026-10-29: disclosed

## References

- [https://rt-labs.com/wp-content/uploads/2026/10/RRTL-261019-01.pdf](https://rt-labs.com/wp-content/uploads/2026/10/RRTL-261019-01.pdf)

## Related threats

- [P-Net buffer over-read in DCP message processing](https://junglewise.ai/threats/cve-2026-115795-p-net-before-1-0-3-does-not-check-that-a-complete-block-header)
- [P-Net buffer over-read in RTA alarm callback](https://junglewise.ai/threats/cve-2026-115794-p-net-before-1-0-3-passes-the-application-alarm-callback-a-data)
- [P-Net RPC session leak leading to denial of service](https://junglewise.ai/threats/cve-2026-115793-p-net-before-1-0-3-does-not-release-the-rpc-session-allocated)
- [P-Net resource exhaustion via malformed RPC requests](https://junglewise.ai/threats/cve-2026-112200-p-net-before-1-0-3-does-not-release-the-application-relationship)
- [P-Net NULL pointer dereference in implicit read request handling](https://junglewise.ai/threats/cve-2026-111736-p-net-before-1-0-3-dereferences-a-null-ar-pointer-in-pf-fspm-cm)