# CVE-2026-115795: Out-of-bounds read of DCP block header in DCP Set and Identify request parsing


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/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-8qv2-6w52-jhrq

## What is CVE-2026-115795?

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

### Official description

P-Net before 1.0.3 does not check that a complete block header is present in the received data before reading the next block in DCP Set and Identify requests. If the last block ends at the end of the receive buffer, the block length of the following block is read past the end of the buffer. In addition, a DCP Set block with a length smaller than the two-byte block qualifier makes the length underflow, so the block is processed with a length of 65534 bytes. This can cause a crash (denial of service) or disclose a small amount of memory content. Requires ADJACENT network access.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-115795 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115795 is a medium-severity vulnerability in RT-Labs P-Net, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115795 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-115795/ (Markdown: https://insights.sbomify.com/CVE-2026-115795/index.md)
```

## Sources

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

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