Skip to main content
VulnerabilityPublished Updated

CVE-2026-67865: S2OPC · CVE-2026-67865 is a high severity

Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

AI-suggested

Until an official fix is available, consider limiting network exposure of affected S2OPC instances and monitoring for abnormal service interruptions related to RepublishResponse handling.

Description

CVE-2026-67865 is a high severity vulnerability in S2OPC version 1.7.3 involving an out-of-bounds read during RepublishResponse handling. This flaw allows a remote attacker to cause a denial of service (DoS) condition. No official patch or remediation guidance is currently available.

References

Community reviews

Loading reviews…