CVE-2026-124762
RPC reject, fault and cancel PDUs abort an Application Relationship
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.
Fixes and workarounds
Fix
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.
Source: CNA: rt-labsWorkaround
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.
Source: CNA: rt-labsAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| P-Net RT-Labs |
≥ 0; < 1.0.4 (affected, semver) ≥ 1.0.4; < * (affected, semver) Other versions: unaffected |
CNA: rt-labs |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 6.0 medium |
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 | CNA: rt-labs |
| 4.0 / 6.0 medium |
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X | NVD: 4b71179a-3b92-4a9d-b9fc-af8b8ed579ee |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://rt-labs.com/wp-content/uploads/2026/11/RRTL-261109-01.pdfCNA: rt-labs
- https://rt-labs.com/wp-content/uploads/2026/11/RRTL-261109-01.pdf4b71179a-3b92-4a9d-b9fc-af8b8ed579ee
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.