# CVE-2026-111730: Out-of-bounds write in CheckPeers block parser due to unvalidated peer station name length


- **Severity:** High 7.2 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/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-w9g9-93r6-xxcf

## What is CVE-2026-111730?

CVE-2026-111730 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 validate the LengthPeerStationName field of a CheckPeers block in get_check_peer(). The received length (up to 255) was used to copy data into the 241-byte peer station name buffer and to place the terminating NUL byte, so a crafted block writes up to 15 bytes past the end of the buffer. This can lead to a crash (denial of service) or potentially arbitrary code execution.

Requires establishment of session that needs ADJACENT network access.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-111730 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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