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

Cato Networks

SDP Client

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-10726 30 Sep 2026 SDP Client: < 6.12.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-10739 30 Sep 2026 SDP Client: < 6.12.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-12374 1 Jul 2026 5.12.0 < 5.13.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-3886 27 Apr 2025 < 5.8.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6978 31 Jul 2024 < 5.10.34 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6977 31 Jul 2024 < 5.10.28 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6975 31 Jul 2024 < 5.10.34 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6974 31 Jul 2024 < 5.10.34 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-6973 31 Jul 2024 < 5.10.34 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.