Skip to main content

open62541 CVE-2026-18785

| EUVDEUVD-2026-52792 LOW
Use After Free (CWE-416)
2026-08-04 VulDB GHSA-vm49-7pv6-899p
1.9
CVSS 4.0 · Vendor: VulDB

Severity by source

Vendor (VulDB) PRIMARY
1.9 MEDIUM
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
vuln.today AI
5.3 MEDIUM

Local-only attack requires low-privilege access to trigger use-after-free in example code; confidentiality and integrity impacts are limited to process memory.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
X

Lifecycle Timeline

4
Analysis Generated
Aug 04, 2026 - 17:38 vuln.today
Severity Changed
Aug 04, 2026 - 17:23 NVD
MEDIUM LOW
CVSS changed
Aug 04, 2026 - 17:23 NVD
4.8 (MEDIUM) 1.9 (LOW)
CVE Published
Aug 04, 2026 - 16:45 cve.org
LOW 1.9

DescriptionCVE.org

A vulnerability was determined in o6 open62541 ca356b088ada7dee824d1b4acd07c1ff07ce242b. Impacted is the function UA_Client_getRemoteDataTypes of the file examples/custom_datatype/client_types_custom.c. Executing a manipulation can lead to use after free. It is possible to launch the attack on the local host. The exploit has been publicly disclosed and may be utilized. The project closed the issue report, stating that this is not the official way to report a security vulnerability.

AnalysisAI

Use-after-free memory corruption in open62541's example client code allows a local low-privileged user to cause memory corruption with potential for denial of service or limited code execution. The vulnerability resides in the UA_Client_getRemoteDataTypes function within the examples/custom_datatype/client_types_custom.c file - notably example/sample code rather than the core library - at commit ca356b088ada7dee824d1b4acd07c1ff07ce242b. A publicly available proof-of-concept exploit exists, though the project closed the issue report citing improper disclosure channel, leaving no official patch or advisory. No confirmed active exploitation (CISA KEV absent), but the CVSS 4.0 E:P modifier reflects the published POC.

Technical ContextAI

open62541 is an open-source C implementation of OPC UA (OPC Unified Architecture), a machine-to-machine communication protocol widely used in industrial automation and ICS/OT environments. The affected code resides in examples/custom_datatype/client_types_custom.c - specifically in the UA_Client_getRemoteDataTypes function, which retrieves remote custom data type definitions from an OPC UA server. CWE-416 (Use After Free) indicates that a memory region is freed and subsequently accessed, yielding a dangling pointer. In C-based OPC UA implementations, data type lifetime management is complex, and incorrect deallocation ordering in client-side type negotiation can expose freed heap memory to subsequent reads or writes. The CPE cpe:2.3:a:o6:open62541:*:*:*:*:*:*:*:* covers all versions of the library, though the specific commit hash ca356b088ada7dee824d1b4acd07c1ff07ce242b narrows the confirmed vulnerable state.

RemediationAI

No vendor-released patch has been identified at time of analysis. The project closed the issue report (https://github.com/open62541/open62541/issues/8131) citing improper disclosure channel, and issued no official fix or advisory. The primary compensating control is to avoid compiling and deploying the examples/custom_datatype/client_types_custom.c example binary in any production or internet-adjacent environment - example code is not hardened for deployment and this file should be excluded from production build targets. If the function UA_Client_getRemoteDataTypes must be used, restrict execution to trusted local users only and enforce OS-level privilege separation to contain any exploit impact. Developers who need the functionality should reimplement it in the core codebase with proper memory lifetime management rather than adapting example code. For organizations that have already deployed binaries derived from this example, auditing memory allocation and deallocation ordering around UA_Client_getRemoteDataTypes is advised, and restricting local access to the host running the client is the most actionable near-term control.

Share

CVE-2026-18785 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy