High · CVSS 8.7CVE-2026-112200

Resource exhaustion from unreleased AR and RPC session on RPC requests with incorrect endiannessCVE-2026-112200

Answer in brief

CVE-2026-112200 records a High severity (CVSS 8.7) vulnerability in Resource exhaustion from unreleased AR and RPC session on RPC requests with incorrect endianness. The current sources do not mark it as known exploited. The current feed maps RT-Labs/P-Net (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 29, 2026Updated Oct 29, 2026Source checked Oct 29, 2026First seen by HOL Oct 29, 2026Material review Oct 29, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.7
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 8.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps RT-Labs/P-Net (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
RT-Labs/P-Netgeneric	>=0 <1.0.3	1.0.3

Recommended response

Check inventory. Check lockfiles and deployed manifests for RT-Labs/P-Net.
Review the reported fix. Source-reported solution: Upgrade to P-Net 1.0.3 or later.

Evidence timeline and material changes

Published upstream
Oct 29, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 29, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 29, 2026

Sources and claim methodology

Source referencert-labs.com

Upstream 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.

Quoted source text, attributed separately from HOL analysis.