Quick answers
- Is CVE-2026-111730 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111730 being exploited in the wild.
- How severe is CVE-2026-111730?
- 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-111730?
- Yes: fixed in P-Net 1.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111730 attacked?
- It is attacked from the adjacent network or over the network, in a software library.
- Am I affected by CVE-2026-111730?
- 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 or later
Technical details
The get_check_peer() function fails to properly validate the LengthPeerStationName field in a CheckPeers block, allowing up to 255 bytes to be written into a 241-byte buffer. An attacker with adjacent network access who can establish a Profinet session can trigger a stack-based buffer overflow that writes 15 bytes past the buffer boundary, corrupting adjacent memory and potentially achieving code execution.
Affected products
- RT Labs P-Net before 1.0.3
Timeline
- 2026-10-29: disclosed