CVE-2026-115795

P-Net before 1.0.3 does not check that a complete block header is present in the received data before reading the next block in DCP Set and Identify requests. If the last block ends at the end of the receive buffer, the block length of the following block is read past the end of the buffer. In...

CVE-2026-115794

P-Net before 1.0.3 passes the application alarm callback a data length derived from the variable part length field of a received RTA alarm frame without checking it against the length of the received frame. A short frame can make the callback receive a length of up to 65507 bytes. An application...

CVE-2026-112200

P-Net before 1.0.3 does not release the Application Relationship AR and the RPC session when an RPC request is rejected because its data representation has incorrect endianness. The session and its AR remain allocated, so repeated requests exhaust the available sessions. Once they are exhausted t...

CVE-2026-115793

P-Net before 1.0.3 does not release the RPC session allocated for an RPC request that names an unknown interface or object UUID, and does not start a timeout for it. Repeated requests with different activity UUIDs exhaust the available sessions. Once they are exhausted the device no longer answer...

CVE-2026-111731

P-Net before 1.0.3 enters an infinite loop when handling a read request for the PDPortDataCheck record with subslot 0 whole module. The loop over the ports never advanced to the next port, so the request never completes and the device stops responding. A remote unauthenticated attacker can use th...

CVE-2026-111730

P-Net before 1.0.3 does not validate the LengthPeerStationName field of a CheckPeers block in getcheckpeer. The received length up to 255 was used to copy data into the 241-byte peer station name buffer and to place the terminating NUL byte, so a crafted block writes up to 15 bytes past the end o...

CVE-2026-111732

P-Net before 1.0.3, when built with PNETOPTIONARVENDORBLOCKS enabled, parses a data length from a field of the ARVendorBlock request that is not part of the block definition and uses it as the number of bytes to copy into a fixed-size buffer, without comparing it with the buffer size or the block...

CVE-2026-111733

P-Net before 1.0.3 dereferences a NULL AR pointer when handling an implicit read request without a valid target AR UUID for a record index that requires an AR AR specific indices 0xE000-0xEFFF, and the expected identification data of a slot or subslot. A remote unauthenticated attacker can send...

CVE-2026-111735

P-Net before 1.0.3 contains an integer underflow in pfcpmcdataind. When handling a received cyclic data frame while the consumer is in the FRUN or RUN state, the offset of the APDU status was computed as the frame length minus 4 using 16-bit arithmetic, without checking that the frame is long...

CVE-2026-111736

P-Net before 1.0.3 dereferences a NULL AR pointer in pffspmcmreadind when handling an implicit read request without a valid target AR UUID for a user specific record index, if the application has registered a read callback. A remote unauthenticated attacker can send such a request to crash the...

CVE-2026-111734

P-Net before 1.0.3 does not validate the length of a received Ethernet frame in pfethrecv before reading the EtherType, any VLAN tags and the PROFINET FrameID. The VLAN tag loop had no upper bound, so a truncated frame, or a frame consisting only of VLAN tags, makes the function read past the end...

CVE-2026-115793

P-Net versions prior to 1.0.3 are vulnerable to a resource exhaustion flaw where the system fails to release RPC sessions allocated for requests naming unknown interface or object UUIDs. Because the system also fails to start a timeout for these requests, a remote unauthenticated attacker can exh...

EUVD-2026-113015

P-Net before 1.0.3 does not release the RPC session allocated for an RPC request that names an unknown interface or object UUID, and does not start a timeout for it. Repeated requests with different activity UUIDs exhaust the available sessions. Once they are exhausted the device no longer answer...

CVE-2026-115794

The P-Net software (versions before 1.0.3 ) is vulnerable to a buffer over-read because it fails to validate the data length of a received RTA alarm frame against the actual frame length. Specifically, the software passes a length derived from the variable part length field to an application alar...

EUVD-2026-113014

P-Net before 1.0.3 passes the application alarm callback a data length derived from the variable part length field of a received RTA alarm frame without checking it against the length of the received frame. A short frame can make the callback receive a length of up to 65507 bytes. An application...

CVE-2026-115795

P-Net versions prior to 1.0.3 are vulnerable to an out-of-bounds read during the parsing of DCP Set and Identify requests. The software fails to verify that a complete block header is present in the received data; if the final block ends at the buffer's edge, the system reads the subsequent block...

EUVD-2026-113013

P-Net before 1.0.3 does not check that a complete block header is present in the received data before reading the next block in DCP Set and Identify requests. If the last block ends at the end of the receive buffer, the block length of the following block is read past the end of the buffer. In...

CVE-2026-111736

The software P-Net versions prior to 1.0.3 is vulnerable to a NULL pointer dereference within the pf_fspm_cm_read_ind() function. This occurs when the system processes an implicit read request that lacks a valid target AR UUID for a user-specific record index, provided the application has registe...

EUVD-2026-113012

P-Net before 1.0.3 dereferences a NULL AR pointer in pffspmcmreadind when handling an implicit read request without a valid target AR UUID for a user specific record index, if the application has registered a read callback. A remote unauthenticated attacker can send such a request to crash the...

CVE-2026-112200

Versions of P-Net before 1.0.3 are vulnerable to a resource exhaustion issue. When an RPC request is rejected due to incorrect data endianness, the software fails to release the Application Relationship (AR) and the RPC session . Repeated requests can exhaust available sessions, causing the devic...