# CVE-2026-82357: RT-Labs AB C-Open CANopen NULL pointer dereference

> A remote attacker with CAN bus access can crash the device by triggering a NULL pointer dereference via the LSS protocol on misconfigured identity objects.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-h298-2mcm-v4fm

## What is CVE-2026-82357?

CVE-2026-82357 is a high-severity vulnerability in RT-Labs AB C-Open, published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

RT-Labs AB C-Open CANopen contains a NULL pointer dereference if the LSS protocol is used to configure the device. An object defined by the user application may not have all required subindexes for object 0x1018. An unauthenticated, remote attacker with access to the CAN bus, through a compromised node for instance, can initiate the LSS protocol on a device with a misconfigured identity object and potentially crash the device. Fixed in 1.1.1.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2026-82357 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82357 is a high-severity vulnerability in RT-Labs AB C-Open, published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82357 in the wild and no public exploit code.

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

## Sources

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

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