# CVE-2026-115793: Resource exhaustion from RPC sessions kept for requests to unknown interface


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-q647-2g3c-gqwj

## What is CVE-2026-115793?

CVE-2026-115793 is a high-severity vulnerability in RT-Labs P-Net, published on 29 Oct 2026. 

### Official description

P-Net before 1.0.3 does not release the RPC session allocated for an RPC request that names an unknown interface or object UUID, and does not start a timeout for it. Repeated requests with different activity UUIDs exhaust the available sessions. Once they are exhausted the device no longer answers new RPC requests, including Endpoint Mapper Lookup and Connect, until it is restarted. A remote unauthenticated attacker can use this to cause a denial of service.

Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime)

## Which versions are affected by CVE-2026-115793?


## How do I fix CVE-2026-115793?

No fix has been published for CVE-2026-115793 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115793 being exploited?

There is no known exploitation of CVE-2026-115793 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115793 and fix it if it is affected.

What it is: CVE-2026-115793 is a high-severity vulnerability in RT-Labs P-Net, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115793 in the wild and no public exploit code.

Affected product: RT-Labs P-Net. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115793/ (Markdown: https://insights.sbomify.com/CVE-2026-115793/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115793
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115793
- OSV: https://osv.dev/vulnerability/CVE-2026-115793

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115793/
Summaries are generated and may contain mistakes; the official description above is the record.