CVE-2026-124762

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.

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

• 6.0CVSS 4.0, Mediumfrom the CNA (rt-labs)CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

What to do

• 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.CNA solution statement
• 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.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

Timeline

1. 13 Nov 2026 Published

Weakness

• CWE-346

References

• Cybersecurity advisory for P-Net