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

Publisher not identified

Intel(R) PROSet/Wireless WiFi software for Windows

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-24911 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24099 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-22887 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20891 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20890 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20886 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20878 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20795 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20789 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20787 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20780 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20778 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20745 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20739 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20737 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20727 11 Aug 2026 See references No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-35971 11 Nov 2025 before version 23.160 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-35967 11 Nov 2025 before version 23.160 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-35963 11 Nov 2025 before version 23.160 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-33029 11 Nov 2025 before version 23.160 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-30255 11 Nov 2025 before version 23.160 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-24512 11 Nov 2025 before version 23.160 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20625 12 Aug 2025 before version 23.110.0.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20618 13 May 2025 before version 23.100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20062 13 May 2025 before version 23.100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20046 13 May 2025 before version 23.100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20039 13 May 2025 before version 23.100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20032 13 May 2025 before version 23.100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20026 13 May 2025 before version 23.100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-20006 13 May 2025 before version 23.100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-35245 13 Nov 2024 before version 23.60 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-33611 13 Nov 2024 before version 23.60 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-33624 13 Nov 2024 before version 23.60 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-40536 16 May 2024 before version 23.20 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-28714 11 Aug 2023 before version 22.220 HF (Hot Fix) An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗

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.