Read the docs

Unchecked RPC PDUs abort Application Relationship in RT-Labs P-Net

Priority LOW 26CWE-346Published · Updated

Key facts

Attack vector
Adjacent network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
Security bypass
Confidentiality · integrity · availability
None · None · High
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-346.

Summary

RT-Labs P-Net before 1.0.4 matches received RPC PDUs to sessions by activity UUID only (CWE-346). A reject, fault or cancel PDU therefore aborts the Application Relationship without checking that it answers a device call or comes from the expected source. A host with adjacent network access that has observed the activity UUID, which is sent in clear in every RPC request, can abort the connection with one PDU.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

P-Net before 1.0.4 finds the RPC session of a received PDU by its activity UUID only, and a reject, fault or cancel PDU for the session aborts the Application Relationship, without checking that the PDU is the answer to a call of the device or where it comes from. A host with ADJACENT network access that has observed the activity UUID of the connection, which is sent in clear in every RPC request, can abort the Application Relationship with one PDU. It also allocates a session for an unknown activity UUID and changes the address stored for an existing session.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00134 2nd percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

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.4; 1.0.4 and later—No fix listedCNA
  • P-Net VendorRT-Labs Affected before 1.0.4; 1.0.4 and later Fixed in — No fix listed 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

The sources list no fixed version for P-Net.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

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.4

    9 records Highest priority Priority LOW 9 LOW

    Other records, highest priority first

    • TI-2026-91525 RPC session pool exhausted by unfinished fragmented requestsPriority LOW 31
    • TI-2026-91523 Out-of-bounds write in RT-Labs P-Net via too many MCR blocksPriority LOW 31
    • TI-2026-91520 Refused IP settings are stored in P-Net DCP Set requestsPriority LOW 30

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-124762
  2. 2026-11-13 Alias added: GHSA-p9h8-2384-wvpg
  3. 2026-11-13 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 37 →

Sources