Read the docs

Out-of-bounds write in RT-Labs P-Net via too many MCR blocks

Priority LOW 31CWE-787Published · Updated

Key facts

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

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

Summary

RT-Labs P-Net before 1.0.4 does not check the number of MCR blocks in a Connect request against the room it has for multicast communication relations, so each extra block is written past the end of the array (CWE-787). An unauthenticated attacker on the adjacent network can trigger this without an established Application Relationship, and the written data comes from the request. Builds with PNET_OPTION_MC_CR disabled are not affected.

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

Description from the CNA

P-Net before 1.0.4 does not check the number of MCR request blocks in a Connect request against the number of multicast communication relations that an Application Relationship has room for (PNET_MAX_MC_CR, 1 by default). Each further block is written past the end of the array, into the rest of the Application Relationship and, with more blocks, into the following one. The written data comes from the request. No established Application Relationship is needed, and the attacker requires ADJACENT network access. Builds with PNET_OPTION_MC_CR disabled are not affected.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00195 9th percentileScored 2026-11-16
Fix Fixed P-Net (RT-Labs): 1.0.4

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.41.0.4Patch availableCNA
  • P-Net VendorRT-Labs Affected before 1.0.4 Fixed in 1.0.4 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.4, which fixes the flaw.

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

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

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-91520 Refused IP settings are stored in P-Net DCP Set requestsPriority LOW 30
    • TI-2026-91518 P-Net accepts RTA alarm frames without checking their sourcePriority LOW 30

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-127122
  2. 2026-11-13 Alias added: GHSA-9cfr-5cg8-55x5
  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