Authentication bypass via subject-length certificate comparison
Published Jun 10, 2026 · Updated Jun 10, 2026
Improper certificate validation in Systerel S2OPC 1.5.0 through 1.7.2 allows remote attackers to establish trusted OPC UA connections. The MbedTLS and CycloneCrypto wrappers compare raw certificate bytes using the subject-name length rather than the full certificate length. Exploitation requires a well-formed certificate that passes every other validation step and matches a trusted entry's subject and total length, causing an untrusted peer to be accepted as trusted.
Summary
What happened
Improper certificate validation in Systerel S2OPC 1.5.0 through 1.7.2 allows remote attackers to establish trusted OPC UA connections. The MbedTLS and CycloneCrypto wrappers compare raw certificate bytes using the subject-name length rather than the full certificate length. Exploitation requires a well-formed certificate that passes every other validation step and matches a trusted entry's subject and total length, causing an untrusted peer to be accepted as trusted.
The record
- CVE
- CVE-2026-9758
- Published
- Jun 10, 2026
- Updated
- Jun 10, 2026
- Vendor
- Systerel
- Product
- S2OPC
- Classifications
- CWE-295, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 2026CVE publishedPublication date reported by the CVE source.
- Jun 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.5.0 <1.7.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- S2OPC trusted-certificate bypass reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo