Live Active security incident? Get immediate response
CVE Record

CVE-2026-9758: Improper Certificate Validation in S2OPC

Improper comparison with the certificates trusted list in S2OPC allows an attacker well-formed untrusted certificate to be considered trusted

HighCVSS 7.3Not KEV-listed Updated
Glexia's Take high

Analyst readout for executives and security teams

Plain-English summary

S2OPC 1.5.0 may wrongly trust a well-formed certificate that is not actually in the trusted list. That can weaken authentication decisions and create risk to confidentiality, integrity, and availability where S2OPC protects network-accessible services.

Executive priority

Treat this as a high-priority dependency validation issue for affected systems. The issue can undermine certificate trust, but current public sources do not show known exploitation or a named patch version.

Technical view

CVE-2026-9758 is CWE-295 improper certificate validation in Systerel S2OPC 1.5.0. The CVE says an improper comparison against the trusted certificate list can cause an untrusted certificate to be considered trusted. CVSS 3.1 is 7.3 with network attack vector, low complexity, no privileges, and no user interaction.

Likely exposure

Exposure is limited to environments running Systerel S2OPC version 1.5.0 in certificate-authenticated paths. The CVE record lists default status as unaffected outside the named affected version, but administrators should confirm deployed package versions and vendor guidance.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not listed as KEV. The CVSS vector indicates remote, unauthenticated attack potential if an attacker can reach the affected service and trigger certificate validation with a well-formed untrusted certificate.

Researcher notes

Public detail is sparse. Focus review on certificate trusted-list comparison behavior in S2OPC 1.5.0 and whether reachable services rely on that decision for authentication or session establishment. Avoid assuming broader version impact without vendor confirmation.

Mitigation direction

  • Check Systerel guidance and the referenced work item for fixed versions or official mitigation.
  • Upgrade S2OPC 1.5.0 when a vendor-supported fixed release is identified.
  • Restrict network access to systems using affected S2OPC certificate validation paths.
  • Review certificate trust lists for stale, unexpected, or overly broad trust entries.
  • Increase monitoring for failed or unusual certificate-based authentication attempts.

Validation and detection

  • Inventory applications and services embedding or deploying S2OPC.
  • Confirm whether any deployed component is S2OPC version 1.5.0.
  • Review dependency manifests, container images, and build artifacts for bundled S2OPC.
  • Map where S2OPC handles certificate-based trust decisions.
  • Check vendor advisories before declaring remediation complete.
Prepared
Confidence
medium
Sources
3

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-295: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-9758 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profile CVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1 CVSS vectors
3 Timeline events
1 ADP providers
2 Source links

SSVC decision data

CISA-ADP CISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

Score Version Severity Vector Exploit Impact Source
7.3 CVSS 3.1 High CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L 3.9 3.4 GitLab

Vulnerability scoring details

Base CVSS 3.1 score

7.3 High
CVSS 3.1 vector shape for CVE-2026-9758 Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reserved CVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE published CVE Program

    The CVE record was published.

  3. CVE updated CVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADP CISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

Vendor Product Version / package Status
Systerel S2OPC 1.5.0 unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-295 · source CWE mapping

Improper Certificate Validation

Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.