What is CVE-2026-67866?
Buffer Overflow vulnerability in Systerel S2OPC 1.7.3 allows a remote attacker to cause a denial of service via the LockedStaMac_ProcessMsg_DeleteMonitoredItemsResponse and SOPC_StaMac_NewDeleteMonitoredItems in the client wrapper DeleteMonitoredItems path
The record classifies CVE-2026-67866 under weakness class CWE-121. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on availability. The identifier was first published 61 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 7.5 — HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - EPSS (FIRST)
- 0.2% probability of exploitation in the next 30 days, higher than 19.6% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 6.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-08-05, last modified 2026-08-06
Is CVE-2026-67866 being exploited?
Weaponised exploit code for CVE-2026-67866 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 43 in the Threadlinqs vulnerability feed.
- trickest/cve (trickest)
Affected products and versions
No affected-product or package list has been recorded for CVE-2026-67866 in the tracked sources. The vendor advisory and the references below are the authoritative statement of what is affected.
How to fix CVE-2026-67866
No vendor patch reference has been recorded for CVE-2026-67866 in the tracked sources. Follow the references below for a fix, and treat any affected deployment as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-67866
No threat campaign in the Threadlinqs corpus currently references CVE-2026-67866, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on .