Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY8 SECURITY RECORDS

Systerel

S2OPC

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-90782 13 Sep 2026 S2OPC: ≤ 1.7.3 S2OPC: 8848f051eed069b107ae7cb16a346d6f6386a8f5 Update reference ↗
CVE-2026-82619 31 Aug 2026 1.7.0; 1.7.1; 1.7.2; 1.7.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-82618 31 Aug 2026 1.7.0; 1.7.1; 1.7.2; 1.7.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-78049 22 Aug 2026 1.7.0; 1.7.1; 1.7.2; 1.7.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-18790 4 Aug 2026 1.7.0; 1.7.1; 1.7.2; 1.7.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-18257 29 Jul 2026 1.5.0 < 2.0.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-9758 10 Jun 2026 1.5.0 < 1.7.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-6899 9 Jun 2026 1.5.0 < 1.7.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.