Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
Upgrade to P-Net 1.0.4 or later, which only handles a reject or fault as the answer to a call of the device and ignores a cancel. It reduces the risk but does not remove it, see Remaining Risk.
Vendor Workaround
Isolate the network of the device from untrusted hosts, for example by a firewall or a separate network,. The remaining risk is that a host that has observed the activity UUID and the sequence number of a pending call of the device can still send a forged reject or fault.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 13 Nov 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | P-Net before 1.0.4 finds the RPC session of a received PDU by its activity UUID only, and a reject, fault or cancel PDU for the session aborts the Application Relationship, without checking that the PDU is the answer to a call of the device or where it comes from. A host with ADJACENT network access that has observed the activity UUID of the connection, which is sent in clear in every RPC request, can abort the Application Relationship with one PDU. It also allocates a session for an unknown activity UUID and changes the address stored for an existing session. | |
| Title | RPC reject, fault and cancel PDUs abort an Application Relationship | |
| Weaknesses | CWE-346 | |
| References |
| |
| Metrics |
cvssV4_0
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: rt-labs
Published:
Updated: 2026-11-13T13:24:25.680Z
Reserved: 2026-11-09T12:48:59.072Z
Link: CVE-2026-124762
No data.
No data.
No data.
OpenCVE Enrichment
No data.