# CVE-2026-82619: Systerel S2OPC subscription_mgr.c use after free

> Remote attackers can trigger a use-after-free in S2OPC's subscription manager, potentially leading to code execution or denial of service.

- **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:P`)
- **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-x4v2-7pqm-v4jq

## What is CVE-2026-82619?

CVE-2026-82619 is a medium-severity use after free 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 identified in Systerel S2OPC up to 1.7.3. The impacted element is the function monitored_item_event_filter_treatment_bs__init_event_filter_ctx_and_result of the file src/ClientServer/services/bgenc/subscription_mgr.c. Such manipulation of the argument EventFilter leads to use after free. The attack may be performed from remote. The exploit is publicly available and might be used. The name of the patch is a4cee16a851b971be447a6ed531173702c722b99. It is best practice to apply a patch to resolve this issue.

Weakness: CWE-416 (Use After Free), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-82619 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82619 is a medium-severity use after free 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-82619 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-82619/ (Markdown: https://insights.sbomify.com/CVE-2026-82619/index.md)
```

## Sources

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

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