Quick answers
- Is CVE-2026-111735 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111735 being exploited in the wild.
- How severe is CVE-2026-111735?
- 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-111735?
- 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-111735 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111735?
- 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 pf_cpm_c_data_ind() function computes an APDU status offset using 16-bit subtraction (frame_length - 4) without validating that the frame is sufficiently long, causing an integer underflow when frames shorter than 4 bytes are processed. An attacker sending a malicious cyclic data frame while the consumer is in FRUN or RUN state triggers out-of-bounds memory reads, enabling denial of service or information disclosure.
Affected products
- rt-labs P-Net before 1.0.3
Timeline
- 2026-10-29: disclosed