# CVE-2026-90782: S2OPC through 1.7.3 NULL Pointer Dereference in alloc_notification_message_items()

> Attackers can cause a denial of service in S2OPC servers by triggering heap allocation failures during notification processing.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **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:** 13 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-wj27-rfm4-9hp4

## What is CVE-2026-90782?

CVE-2026-90782 is a medium-severity vulnerability in Systerel S2OPC, published on 13 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

S2OPC through 1.7.3 contains a null pointer dereference in msg_subscription_publish_bs__alloc_notification_message_items() where a failed allocation for DataChangeNotification is overwritten by a successful allocation for EventNotificationList. Attackers can trigger heap allocation failures on sessions with both data-change and event notifications to cause the server process to terminate.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2026-90782 being exploited?

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

Public exploit code:

- Standalone PoC for CVE-2026-90782: status-clobbering NULL dereference in S2OPC alloc_notification_message_items() (DataChange fails, Event succeeds) (github_poc): https://github.com/HarshRajSinghania/CVE-2026-90782-s2opc-status-clobber

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90782 is a medium-severity vulnerability in Systerel S2OPC, published on 13 Sep 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-90782 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-90782/ (Markdown: https://insights.sbomify.com/CVE-2026-90782/index.md)
```

## Sources

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

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