CVE-2026-67860: open62541 · Heap-based Buffer Overflow
Affects open62541Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubopen62541/open62541pkg:github/open62541/open62541Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, users should consider avoiding use of the default HistoryRead path with the memory backend or apply any recommended workarounds from the vendor once published.
Description
open62541 version 1.5.5 contains a heap-based buffer overflow vulnerability in the default HistoryRead path when using the default history database with the memory backend. This vulnerability can lead to a denial of service due to application crash. The issue is identified as CWE-122 and has a CVSS 3.1 base score of 7.5, indicating high severity. There is no vendor advisory or patch information currently available.