Resource exhaustion from unreleased AR and RPC session on RPC requests with incorrect endianness
Impact
P-Net before 1.0.3 is vulnerable to resource exhaustion from unreleased sessions due to RPC requests with incorrect endianness, allowing a remote unauthenticated attacker to cause a denial of service. The sessions remain allocated, exhausting available sessions. A restart is required to recover.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.What to do
Upgrade to P-Net 1.0.3 or later.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
RT-Labs · rt-labs
P-Net
1 range
RT-Labs · rt-labs
P-Net
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → before 1.0.3
semver versions
Other versions: unaffected
Original source description
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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-112200View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.