Vulnerability in RT-Labs AB C-Open CANopen (CVE-2026-82357)
Summary
Vulnerability in RT-Labs AB C-Open CANopen (CVE-2026-82357). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.1.1 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-82357 has been found in RT-Labs AB C-Open CANopen.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade RT-Labs AB C-Open CANopen to 1.1.1 or later.
If unsure, ask your IT team or search "RT-Labs AB C-Open CANopen CVE-2026-82357" on the vendor's site.
CVE-2026-82357 (RT-Labs AB C-Open CANopen) — CWE-476 / CVSS v3 6.5
Attack vector: adjacent-network / unauthenticated / no user interaction
Patched: 1.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-476) exists in RT-Labs AB C-Open CANopen.
Check the vendor advisory for the affected versions of RT-Labs AB C-Open CANopen.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 1.1.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで RT-Labs AB C-Open CANopen を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade RT-Labs AB C-Open CANopen to 1.1.1ステージング環境で 1.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com
- web raw.githubusercontent.com
- web rt-labs.com
- web cve.org
- web nvd.nist.gov
- web github.com