Quick answers
- Is CVE-2026-90782 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90782 being exploited in the wild.
- How severe is CVE-2026-90782?
- Medium severity, with a CVSS score of 5.3, published 13 September 2026.
- Which products and versions are affected?
- Systerel S2OPC through 1.7.3.
- Is there a fix for CVE-2026-90782?
- 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-90782 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-90782?
- 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
The vulnerability is a null pointer dereference in msg_subscription_publish_bs__alloc_notification_message_items() where a failed memory allocation for DataChangeNotification is incorrectly overwritten by a subsequent successful allocation for EventNotificationList. This occurs in sessions configured with both data-change and event subscription notifications. An attacker with network access to an OPC UA server can trigger controlled heap allocation failures, causing the server process to terminate (denial of service). The flaw affects S2OPC versions through 1.7.3 and requires no authentication beyond OPC UA session access.
Affected products
- Systerel S2OPC through 1.7.3
Timeline
- 2026-09-13: disclosed