Skip to main content

S2OPC CVE-2026-18257

| EUVDEUVD-2026-50410 MEDIUM
Improper Certificate Validation (CWE-295)
2026-07-29 GitLab GHSA-xph3-r29g-fwfg
5.6
CVSS 3.1 · Vendor: GitLab
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain network MitM position on OT segment
  2. Delivery
    Intercept TLS handshake between S2OPC endpoints
  3. Exploit
    Present certificate chain rooted in expired CA
  4. Execution
    S2OPC skips root validity period check
  5. Persist
    Certificate accepted as trusted
  6. Impact
    Intercept or inject OPC UA session data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V12 - Secure Communication Certificate validation
Exploitation Conditions

Exploitation requires the attacker to occupy a network-adjacent or on-path position between communicating S2OPC endpoints - passive sniffing alone is insufficient; active traffic interception (MitM) is necessary. Additionally, the attack is only viable when at least one expired root CA certificate is present in the S2OPC trusted certificate store, as the flaw specifically concerns the omission of validity period enforcement on root issuers; if all trusted root CAs hold current validity periods, the exploitable condition does not arise in practice. Affected deployment versions are S2OPC 1.5.0 through 1.x prior to 2.0.0. No authentication by the attacker to the S2OPC instance is required per the CVSS PR:N metric, but the MitM positioning prerequisite materially limits opportunistic exploitation.

Impact

The NVD CVSS 3.1 score of 5.6 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L) reflects meaningful but bounded risk. AC:H correctly captures the prerequisite of network positioning for a man-in-the-middle attack, significantly reducing exploitability compared to a direct unauthenticated flaw. No EPSS score was provided in the intelligence feed, so exploitation probability cannot be quantified; no KEV listing and no public POC further reduce urgency. The CIA triple of L/L/L reflects partial impact: an attacker who successfully bypasses certificate validation can intercept or tamper with OPC UA session data but cannot fully compromise the host or cause catastrophic data destruction in isolation. However, in operational technology (OT) and ICS environments where S2OPC is typically deployed, even low-integrity tampering of industrial protocol messages can have outsized safety or process consequences disproportionate to the raw CVSS score. Risk should be elevated in environments where S2OPC handles safety-instrumented systems or process control. There is no conflict between the CVSS vector and the vulnerability description.

Exploit ScenarioDerived

An attacker with network access between an S2OPC client and server - for example via ARP poisoning, rogue access point, or compromised network switch on an OT segment - presents a TLS certificate signed by an expired root CA that the legitimate S2OPC peer has in its trust store. Because S2OPC's CycloneCrypto wrapper skips the validity period check on the root issuer, the certificate is accepted as trusted, enabling the attacker to establish a trusted OPC UA session and intercept or inject industrial protocol messages. No public proof-of-concept has been identified, but the logic flaw is straightforward to exploit once MitM positioning is achieved.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 29, 2026

Certificate trust bypass in S2OPC versions 1.5.0 through 1.x (prior to 2.0.0) allows a remote attacker to have certificates signed by an expired root CA accepted as fully trusted due to missing validity period enforcement in the CycloneCrypto wrapper layer. The flaw affects OPC UA communications protected by this library, enabling potential interception or tampering of industrial protocol traffic. No public exploit code has been identified at time of analysis, and the vulnerability has not been added to the CISA KEV catalog.

RemediationAI

Upgrade to S2OPC 2.0.0 or later, which contains the vendor-released patch for this flaw; this is the primary and recommended remediation. The upstream fix discussion is tracked at https://gitlab.com/systerel/S2OPC/-/work_items/1804. If an immediate upgrade is not feasible, operators should audit their deployed PKI to remove or rotate any root CA certificates that are expired or approaching expiry, since the vulnerability is only exploitable when an expired root CA certificate exists in the trusted store. Additionally, network-layer controls restricting OPC UA (typically TCP port 4840) to known, authenticated endpoints via firewall or network segmentation will raise the bar for MitM positioning and reduce the attack surface. These compensating controls do not eliminate the underlying flaw and should be treated as temporary mitigations only until the patch is applied.

Affected VersionsENISA

S2OPC 1.5.0 <2.0.0

Affected Packages

euvd s2opc fix: 2.0.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

S2OPC (Safe and Secure OPC-UA) is Systerel's open-source OPC UA stack designed for safety-critical and industrial control system deployments. It relies on CycloneCrypto as its cryptographic backend for PKI operations, including certificate chain validation. CWE-295 (Improper Certificate Validation) describes the root cause: the certificate validation routine fails to enforce the notBefore/notAfter validity window when evaluating a root issuer (CA) certificate. Under the X.509 standard, root CA certificates carry strict validity periods, and accepting an expired root allows any leaf certificate signed by that expired CA to masquerade as trusted. The CPE string cpe:2.3:a:systerel:s2opc:*:*:*:*:*:*:*:* and EUVD-2026-50410 confirm the affected product family spans the 1.5.0 release series up to but not including 2.0.0.

Know when S2Opc gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitLab) PRIMARY 5.6 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
vuln.today AI 5.6 MEDIUM

Agrees with provided vector: MitM positioning raises AC:H; no attacker authentication needed (PR:N); partial CIA impacts from session interception on a scoped OPC UA connection.

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

Primary rating from Vendor (GitLab).

CVSS VectorVendor: GitLab

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Lifecycle Timeline

1
Patch available
Jul 29, 2026 - 17:02 EUVD

DescriptionCVE.org

Improper validity period check for root issuer certificate in CycloneCrypto cryptographic wrapper of S2OPC allows a certificate issued by this root issuer to be considered trusted

Threat Intelligence Overview

EPSS Score
0.1%
Top 99% exploitable
Prevalence
Low
niche OPC UA stack primarily for ICS/safety-critical deployments
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

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