CVE-2026-18790
Received Received - Intake

Out-of-Bounds Read in Systerel S2OPC

Vulnerability report for CVE-2026-18790, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-04

Last updated on: 2026-08-04

Assigner: VulDB

Description

A weakness has been identified in Systerel S2OPC up to 1.7.3. This affects the function LockedStaMac_ProcessMsg_DeleteMonitoredItemsResponse of the file src/ClientServer/frontend/client_wrapper/internal/state_machine.c of the component DeleteMonitoredItemsRequest Handler. This manipulation causes out-of-bounds read. The attack can only be executed locally. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-04
Last Modified
2026-08-04
Generated
2026-08-04
AI Q&A
2026-08-04
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
systerel s2opc to 1.7.3 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-119 The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
CWE-125 The product reads data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an out-of-bounds read in Systerel S2OPC up to version 1.7.3. It occurs in the DeleteMonitoredItemsRequest Handler when processing a DeleteMonitoredItemsResponse message. The issue arises because the client wrapper does not validate the number of results in the server's response against the original request, leading to an attempt to access non-existent array elements. This causes a heap-based out-of-bounds read, which can crash the client application.

Detection Guidance

Detecting this vulnerability requires monitoring for crashes in S2OPC client applications during DeleteMonitoredItemsResponse processing. Check logs for heap corruption errors or segmentation faults in S2OPC clients. No specific commands are provided in the context, but monitoring OPC UA client application stability and network traffic for malformed responses may help.

Impact Analysis

This vulnerability can cause denial-of-service by crashing the client application. Since the attack can only be executed locally, it requires an attacker to have access to the system running the vulnerable S2OPC client. The exploit could lead to application instability or termination, disrupting operations that depend on the OPC UA communication protocol.

Mitigation Strategies

Immediately update S2OPC to the latest version beyond 1.7.3 if available. If no patch exists, restrict network access to OPC UA servers, disable DeleteMonitoredItemsRequest functionality if possible, and monitor client applications for crashes. The vendor did not respond, so consider alternative OPC UA implementations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-18790. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart