Live › vulnerability › CVE-2026-112200
P-Net, an open-source PROFINET device stack, does not release the Application Relationship and RPC session when an RPC request with wrong data endianness is rejected. Repeated requests exhaust the available sessions, so the device stops answering new RPC requests, including Connect, until restarted.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 16:25 UTC. All times on this page are UTC.
Devices built on P-Net before version 1.0.3 that accept PROFINET RPC requests on the network are exposed. The sources do not list the specific products or vendors that embed P-Net, so teams should check whether any industrial controllers or field devices in their environment run it. Systems that do not run P-Net, or that filter PROFINET traffic from untrusted networks, can skip it.
No product ranges from the sources yet.
1.0.3.1.0.3 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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 the device no longer answers new RPC requests, including Connect, until it is restarted. A remote unauthenticated attacker can use this to cause a denial of service.
This page as .md · .json · in your agent: get_signal("CVE-2026-112200")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.