CVE-2026-82946 Null Pointer Dereference in Mailbox Error Handling
Medium 6.5
Published
Updated
Check this codebase for CVE-2026-82946 and fix it if it is affected.
What it is: CVE-2026-82946 is a medium-severity vulnerability in RT-Labs AB SOEM, published on 26 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-82946 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-82946/ (Markdown: https://insights.sbomify.com/CVE-2026-82946/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-82946?
CVE-2026-82946 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 a vulnerability where a malicious device can crash the master system. When the software receives an error response, it clears an internal pointer but continues processing. If another message arrives before timeout, the software attempts to use the cleared pointer, causing a crash. An attacker can trigger this with a simple sequence of two messages.
Which versions are affected by CVE-2026-82946?
How do I fix CVE-2026-82946?
No fix has been published for CVE-2026-82946 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-82946 being exploited?
There is no known exploitation of CVE-2026-82946 in the wild and no public exploit code.
Sources
Also known as GHSA-m2qv-7w8c-3r6g.