# CVE-2026-82618: Systerel S2OPC String Array Range Writing sopc_builtintypes.c set_range_matrix_on_string_array out-of-bounds

> Remote attackers can trigger an out-of-bounds read in S2OPC, potentially exposing memory or causing crashes.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-cpqm-m568-8qmx

## What is CVE-2026-82618?

CVE-2026-82618 is a medium-severity memory corruption vulnerability in Systerel S2OPC, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in Systerel S2OPC up to 1.7.3. The affected element is the function set_range_matrix_on_string_array of the file src/Common/opcua_types/sopc_builtintypes.c of the component String Array Range Writing. This manipulation causes out-of-bounds read. The attack is possible to be carried out remotely. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-82618 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82618 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82618 is a medium-severity memory corruption vulnerability in Systerel S2OPC, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82618 exists.

Affected product: Systerel S2OPC. 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-82618/ (Markdown: https://insights.sbomify.com/CVE-2026-82618/index.md)
```

## Sources

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

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