# CVE-2026-82947: Multiple Out-of-Bounds Reads in Frame Processing


- **Severity:** High 7.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-fq96-jx7g-9639

## What is CVE-2026-82947?

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

### Official description

SOEM version 2.0.0 and earlier contains multiple vulnerabilities in frame processing where a malicious device can cause the master to read data outside allocated buffers. The software uses length and offset values from device messages without validating them against buffer sizes. This can cause the master to access invalid memory locations, potentially disclosing sensitive information or causing crashes.

Weakness: CWE-787 (Out-of-bounds Write), CWE-191 (Integer Underflow (Wrap or Wraparound)), CWE-129 (Improper Validation of Array Index), CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-82947 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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