Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain network MitM position on OT segment
-
DeliveryIntercept TLS handshake between S2OPC endpoints
-
ExploitPresent certificate chain rooted in expired CA
-
ExecutionS2OPC skips root validity period check
-
PersistCertificate accepted as trusted
-
ImpactIntercept 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
Primary rating from Vendor (GitLab).
CVSS VectorVendor: GitLab
Lifecycle Timeline
1DescriptionCVE.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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Improper certificate trust validation in Systerel S2OPC allows remote attackers to have well-formed but untrusted X.509
Out-of-bounds read in S2OPC's AddNodes service allows remote attackers to trigger memory read violations via a crafted U
Use-after-free in Systerel S2OPC OPC UA stack up to version 1.7.3 allows remote low-privileged attackers to crash the OP
Null pointer dereference in Systerel S2OPC through version 1.7.3 enables authenticated remote clients to crash the OPC-U
Out-of-bounds read in Systerel S2OPC versions 1.7.0 through 1.7.3 allows a local, low-privileged attacker to disrupt the
Improper certificate revocation checking in S2OPC's CycloneCrypto wrapper permits OPC UA connections authenticated with
EUVD-2026-50410
GHSA-xph3-r29g-fwfg
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB