Live › vulnerability › CVE-2026-115793
P-Net, a PROFINET device stack, leaves the RPC session open when a request names an unknown interface or object UUID and never times it out. Repeated requests exhaust the sessions, so the device stops answering RPC requests until it is restarted, which is a remote denial of service.
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.
Industrial or embedded devices that run P-Net before 1.0.3 and accept PROFINET RPC traffic from the network. Systems where PROFINET is kept on an isolated segment, or devices that do not use P-Net, can skip it. The sources do not name specific products.
No product ranges from the sources yet.
unknown if the sources do not say how to read it1.0.3 or laterEach 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 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 answers new RPC requests, including Endpoint Mapper Lookup and 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-115793")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.