RPC session pool exhausted by unfinished fragmented requests
Key facts
- Attack vector
- Adjacent network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-772.
Summary
RT-Labs P-Net before 1.0.4 keeps RPC sessions allocated for request fragments with an unknown activity UUID and no timeout, when the rest of the request never arrives. Sessions that never receive an Application Relationship are also kept after the response, a missing release of resources after the effective lifetime (CWE-772). An unauthenticated attacker with adjacent network access can send repeated fragments or requests with different activity UUIDs to exhaust the available sessions, after which the device no longer answers Connect requests until it is restarted, causing a denial of service.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Description from the CNA
P-Net before 1.0.4 keeps the RPC session that is allocated for a fragment of a request with an unknown activity UUID, without a timeout, when the rest of the request never arrives. A session that does not get an Application Relationship is also kept after the response. Repeated fragments or requests with different activity UUIDs exhaust the available sessions, one UDP packet per session. Once they are exhausted the device no longer answers a Connect request until it is restarted. An unauthenticated attacker with ADJACENT network access can use this to cause a denial of service.
Why it matters now
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
Remediation
Update P-Net to version 1.0.4 or later, which fixes this flaw. The sources list no fixed version for any other product.
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-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
- TI-2026-91518 P-Net accepts RTA alarm frames without checking their sourcePriority LOW 30
Timeline
- 2026-11-13 Threatist record created from CVE-2026-127124
- 2026-11-13 Alias added: GHSA-9h8r-54hw-6fp8
- 2026-11-13 CISA SSVC decision points changed
References
More RT-Labs vulnerabilities
- 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
Sources
- CVE-2026-127124 · CVE Program
- CVE-2026-127124 · NVD
- FIRST EPSS
- GHSA-9h8r-54hw-6fp8 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences