Server crash via forged Acknowledge method metadata
Published Aug 5, 2026 · Updated Aug 5, 2026
Type confusion in open62541 1.5.5 allows remote attackers to crash an OPC UA server through a crafted Acknowledge method call. Service_Call validates arguments against mutable InputArguments metadata, but acknowledgeMethodCallback casts the first value to UA_ByteString without rechecking its type. Exploitation requires a session permitted to modify method metadata; a forged Boolean is read as a ByteString, causing an out-of-bounds read and server crash.
Summary
What happened
Type confusion in open62541 1.5.5 allows remote attackers to crash an OPC UA server through a crafted Acknowledge method call. Service_Call validates arguments against mutable InputArguments metadata, but acknowledgeMethodCallback casts the first value to UA_ByteString without rechecking its type. Exploitation requires a session permitted to modify method metadata; a forged Boolean is read as a ByteString, causing an out-of-bounds read and server crash.
The record
- CVE
- CVE-2026-67869
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 2026CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Acknowledge metadata-tampering PoC clientproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo