# CVE-2026-115794: Alarm data length not validated against received frame length


- **Severity:** Low 2.3 (`CVSS:4.0/AV:A/AC:L/AT:P/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-vmq4-4rhp-6cqg

## What is CVE-2026-115794?

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

### Official description

P-Net before 1.0.3 passes the application alarm callback a data length derived from the variable part length field of a received RTA alarm frame without checking it against the length of the received frame. A short frame can make the callback receive a length of up to 65507 bytes. An application that copies the reported number of bytes reads past the end of the receive buffer. The attacker must have established an Application Relationship and requires ADJACENT network access. Applications that do not use the alarm data are not affected.

Weakness: CWE-130 (Improper Handling of Length Parameter Inconsistency)

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


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

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

## Is CVE-2026-115794 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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