CVE-2026-127124 in P-Netinfo

Summary

by MITRE • 11/13/2026

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.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/13/2026

The vulnerability in P-Net versions prior to 1.0.4 represents a critical resource exhaustion flaw rooted in improper session management within the Remote Procedure Call (RPC) subsystem. The core technical deficiency lies in the application's handling of fragmented network requests and incomplete interactions. Specifically, when the system receives an initial fragment of an RPC request containing an unknown activity UUID, it allocates a dedicated UDP session to track this interaction. Under normal operational conditions, subsequent fragments or the completion of the request would resolve this state. However, if the remainder of the request fails to arrive due to network issues or malicious intent, the system retains this allocated session indefinitely without implementing any timeout mechanism. This lack of an expiration policy means that stale sessions persist in memory and connection tables, consuming finite resources intended for legitimate traffic.

Furthermore, the flaw extends beyond incomplete requests to include responses associated with Application Relationships that are never established. Even after a response is sent, if no valid application relationship was formed during the exchange, the session remains active rather than being cleaned up. This behavior creates two distinct vectors for resource depletion: one driven by fragmented packets and another by incomplete handshake sequences. An attacker can exploit these mechanisms to systematically consume available UDP sessions. Since each malicious or malformed interaction consumes exactly one UDP packet slot per session, an unauthenticated adversary with adjacent network access can rapidly exhaust the device's capacity to handle new connections. The attack does not require authentication, significantly lowering the barrier for exploitation and allowing any nearby entity on the same network segment to initiate the denial of service.

The operational impact of this vulnerability is a complete loss of availability for the P-Net device. Once the pool of available sessions is depleted by repeated fragments or requests with varying activity UUIDs, the device becomes unable to process new Connect requests. This effectively renders the device unresponsive to legitimate management and control operations until it undergoes a manual restart. In industrial automation environments where P-Net is commonly deployed for real-time communication between controllers and field devices, such an outage can lead to significant production halts or safety risks if critical monitoring functions are disrupted. The inability to accept new connections persists indefinitely without administrative intervention, making this a persistent denial of service condition rather than a transient glitch.

From a classification perspective, this vulnerability aligns with CWE-400, which describes Uncontrolled Resource Consumption, specifically manifesting as resource exhaustion through session leakage. It also maps to the MITRE ATT&CK technique T1499, Endpoint Denial of Service, where an attacker degrades or disrupts the availability of a target system by consuming its resources. To mitigate this risk, organizations running P-Net versions earlier than 1.0.4 should prioritize upgrading to version 1.0.4 or later, which addresses these session management flaws. In environments where immediate patching is not feasible, network segmentation strategies can be employed to restrict adjacent access to the vulnerable devices, thereby limiting the attack surface for unauthenticated actors. Additionally, implementing strict rate-limiting on UDP traffic and configuring firewall rules to drop fragmented packets with unknown identifiers can provide a temporary layer of defense against this specific exhaustion vector until the software update is applied.

Responsible

Rt-labs

Reservation

11/12/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00204

KEV

no

Activities

very low

Sources

Do you need the next level of professionalism?

Upgrade your account now!