Open62541 SDK Vulnerability Allows Remote Code Execution
A use-after-free vulnerability in the open62541 SDK, assigned CVE-2026-126962, allows authenticated remote attackers to execute arbitrary code.

The open62541 SDK, a popular open-source implementation of the OPC UA communication protocol, is affected by a critical use-after-free vulnerability that could allow remote attackers to execute arbitrary code on vulnerable systems. The vulnerability, tracked as CVE-2026-126962, was disclosed by the Zero Day Initiative (ZDI) and carries a CVSS score of 8.8, indicating high severity.
The core of the vulnerability lies in how open62541 handles subscriptions. Specifically, the flaw arises from a failure to properly validate the existence of an object before performing operations on it. This oversight can lead to a use-after-free condition, where the program attempts to access memory that has already been deallocated, a common precursor to memory corruption and arbitrary code execution.
To exploit this vulnerability, an attacker must first be authenticated to the open62541 service. Once authenticated, they can craft malicious requests that trigger the use-after-free condition. Successful exploitation would allow the attacker to execute code within the context of the service account running the open62541 application, potentially leading to full system compromise.
The Zero Day Initiative reported the vulnerability to the vendor on June 17, 2026, and a coordinated public release of the advisory occurred on November 13, 2026. The advisory was updated on the same day. The vulnerability was discovered by Andrew Letourneau.
While the specific impact and widespread exploitation of this vulnerability are not yet fully detailed, its high CVSS score and the nature of the flaw suggest a significant risk to organizations relying on open62541 for industrial control systems, IoT devices, and other applications that utilize the OPC UA standard.
Mitigation efforts are underway, with developers having released commits to address the issue. Users of open62541 are strongly advised to review the provided commit links (https://github.com/open62541/open62541/commit/2da371bcdaadeb23051635a60e38f31039af9fd8, https://github.com/open62541/open62541/commit/bc30df3adab5cc61383cb7e7f551bfd6f7ac160c) and apply necessary patches or updates as soon as possible.
This vulnerability underscores the ongoing security challenges in the Industrial Internet of Things (IIoT) and operational technology (OT) sectors, where robust and secure communication protocols are paramount. The open-source nature of libraries like open62541 offers flexibility and transparency but also necessitates diligent security auditing and prompt patching by users.