# CVE-2026-82943: Out-of-Bounds Read via Unchecked Length Values


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-2h24-jp9f-47qx

## What is CVE-2026-82943?

CVE-2026-82943 is a medium-severity vulnerability in RT-Labs AB SOEM, published on 26 Oct 2026. 

### Official description

SOEM version 2.0.0 and earlier contains vulnerabilities where a malicious device can send messages that cause the master to read data from memory locations beyond the intended buffer. The software uses length values from device responses without validating them against actual buffer sizes. An attacker can exploit this to extract up to 64KB of data from the master's memory.

Weakness: CWE-195 (Signed to Unsigned Conversion Error), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-82943 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82943 is a medium-severity vulnerability in RT-Labs AB SOEM, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-82943 in the wild and no public exploit code.

Affected product: RT-Labs AB SOEM. 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-82943/ (Markdown: https://insights.sbomify.com/CVE-2026-82943/index.md)
```

## Sources

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

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