Authentication bypass via first-match CRL validation
Published Jun 9, 2026 · Updated Jun 9, 2026
Certificate revocation bypass in Systerel S2OPC 1.5.0 through 1.7.2 allows remote attackers to connect with a revoked certificate. The crt_verifycrl_and_check_revocation function stops after the first valid CRL for a CA instead of checking every valid CRL, so a later revocation entry is ignored. Exposure requires the CycloneCrypto wrapper and multiple valid CRLs for the same CA; the result is an OPC UA connection that should be rejected.
Summary
What happened
Certificate revocation bypass in Systerel S2OPC 1.5.0 through 1.7.2 allows remote attackers to connect with a revoked certificate. The crt_verifycrl_and_check_revocation function stops after the first valid CRL for a CA instead of checking every valid CRL, so a later revocation entry is ignored. Exposure requires the CycloneCrypto wrapper and multiple valid CRLs for the same CA; the result is an OPC UA connection that should be rejected.
The record
- CVE
- CVE-2026-6899
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- Systerel
- Product
- S2OPC
- Classifications
- CWE-299, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 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
No public exploit references are available in this record.
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