Read the docs

Alarm data length not validated in RT-Labs P-Net

Priority LOW 11CWE-130Published · Updated

Key facts

Attack vector
Adjacent network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
Low · None · Low
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

P-Net before 1.0.3 from RT-Labs passes the application alarm callback a data length taken from the variable part length field of a received RTA alarm frame without checking it against the received frame length. A short frame can make the callback receive a length of up to 65507 bytes, and an application that copies that many bytes reads past the end of the receive buffer, which is a missing length check (CWE-130). An attacker must have established an Application Relationship and have adjacent network access. Only applications that use the alarm data are affected.

Written with Claude Haiku 5.5 from the sources below · 2026-10-30

Description from the CNA

P-Net before 1.0.3 passes the application alarm callback a data length derived from the variable part length field of a received RTA alarm frame without checking it against the length of the received frame. A short frame can make the callback receive a length of up to 65507 bytes. An application that copies the reported number of bytes reads past the end of the receive buffer. The attacker must have established an Application Relationship and requires ADJACENT network access. Applications that do not use the alarm data are not affected.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00176 7th percentileScored 2026-11-07
Fix Fixed P-Net (RT-Labs): 1.0.3

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
RT-LabsP-Netbefore 1.0.31.0.3Patch availableCNA
  • P-Net VendorRT-Labs Affected before 1.0.3 Fixed in 1.0.3 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:rt-labs:p-net:*:*:*:*:*:*:*:*——RT-Labs
  • cpe:2.3:a:rt-labs:p-net:*:*:*:*:*:*:*:* Versions — — ·RT-Labs

Remediation

Update RT-Labs P-Net to version 1.0.3 or later, which fixes the flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-10-30

  • Fix · CNA P-Net (RT-Labs) Fixed in 1.0.3

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    RT-Labs P-Net 1.0.3

    11 records Highest priority Priority MEDIUM 5 MEDIUM, 6 LOW

    Other records, highest priority first

    • TI-2026-82626 Out-of-bounds write when parsing AR Vendor Block requests in RT-Labs P-NetPriority MEDIUM 48
    • TI-2026-82632 Resource exhaustion from RPC sessions kept for unknown interface requestsPriority MEDIUM 44
    • TI-2026-82630 NULL pointer dereference in RT-Labs P-Net on implicit read requestsPriority MEDIUM 44

Timeline

  1. 2026-10-29 Threatist record created from CVE-2026-115794
  2. 2026-10-29 Alias added: GHSA-vmq4-4rhp-6cqg
  3. 2026-11-05 CISA SSVC decision points changed

References

  • TI-2026-82626 Out-of-bounds write when parsing AR Vendor Block requests in RT-Labs P-Net CVSS 4.0CRITICAL 9.3
  • TI-2026-82632 Resource exhaustion from RPC sessions kept for unknown interface requests CVSS 4.0HIGH 8.7
  • TI-2026-82630 NULL pointer dereference in RT-Labs P-Net on implicit read requests CVSS 4.0HIGH 8.7
  • TI-2026-82627 NULL pointer dereference in P-Net lets remote attackers crash devices CVSS 4.0HIGH 8.7
  • TI-2026-82625 Infinite loop in RT-Labs P-Net PDPortDataCheck record handling CVSS 4.0HIGH 8.7
  • TI-2025-23482 Out-of-bounds write in RT-Labs P-Net CVSS 3.1CRITICAL 9.8
See all 28 →

Sources