Read the docs

P-Net accepts RTA alarm frames without checking their source

Priority LOW 30CWE-346Published · Updated

Key facts

Attack vector
Adjacent network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
None · Low · 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 from 0 before 1.0.4 and from 1.0.4 before * is affected. P-Net routes a received RTA alarm frame to an Application Relationship using only the destination alarm reference, without checking the frame's source (CWE-346). An attacker with adjacent network access can abort an established Application Relationship with one alarm ERROR frame, or send forged alarm notifications to the application.

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

Description from the CNA

P-Net before 1.0.4 routes a received RTA alarm frame to an Application Relationship using only the destination alarm reference in the frame, without checking the source of the frame. A host with ADJACENT network access can abort an established Application Relationship with a single alarm ERROR frame, or deliver forged alarm notifications with chosen type, slot, subslot, USI and payload to the application.

Why it matters now

EPSS 0.00106 1st percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

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-124759
  2. 2026-11-13 Alias added: GHSA-fgx3-4328-fm5x

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