Quick answers
- Is CVE-2026-82618 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82618 being exploited in the wild.
- How severe is CVE-2026-82618?
- Medium severity, with a CVSS score of 4.3, published 31 August 2026.
- Which products and versions are affected?
- Systerel S2OPC up to 1.7.3.
- Is there a fix for CVE-2026-82618?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82618 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-82618?
- Check whether you run Systerel S2OPC at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A heap-based out-of-bounds read vulnerability exists in the `set_range_matrix_on_string_array()` function in src/Common/opcua_types/sopc_builtintypes.c. When processing two-dimensional OPC UA IndexRange writes to String[] values, the function derives the number of source elements to process from the first dimension of the destination range, but fails to verify that the source array contains the same number of elements. An attacker can send a malformed OPC UA Write service request specifying a range larger than the provided source array; the server then dereferences out-of-bounds String objects, reading uninitialized or adjacent heap memory. The vulnerability is remotely exploitable without authentication and causes immediate server crash (denial of service). No patch has been released as of the advisory date.
Affected products
- Systerel S2OPC up to 1.7.3
Timeline
- 2026-08-31: disclosed