# CVE-2026-127125: NULL pointer dereference when a response fragment is not acknowledged


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:A/AC:L/AT:P/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:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-88cc-w8xr-wfmh

## What is CVE-2026-127125?

CVE-2026-127125 is a medium-severity vulnerability in RT-Labs P-Net, published on 13 Nov 2026. 

### Official description

P-Net before 1.0.4 aborts the Application Relationship of an RPC session when a fragment of a response has been resent without being acknowledged, without checking that the session has an Application Relationship. A request for an existing Application Relationship that is sent on another activity than its Connect, and gets a fragmented response, is handled on a session without one. If the response is not acknowledged, a NULL pointer is dereferenced and the device crashes. A conformant IO-controller does not send such requests. The attacker must have observed the AR UUID of an established Application Relationship and requires ADJACENT network access.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2026-127125 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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