Safeguard
Vulnerability Analysis•

CVE-2026-20891: High Improper Auth in Intel PROSet Wi-Fi Driver

CVE-2026-20891: high severity (7.9) Intel Wi-Fi software flaw. Update PROSet/Wireless Wi-Fi software to 24.10 or later; Intel scores it 6.3 on CVSS 4.0.

Safeguard Security Team
4 min read

CVE-2026-20891 is a high severity (CVSS 7.9 in the record) flaw in Intel PROSet/Wireless Wi-Fi software for Windows: a driver that does not properly authenticate a caller. It can lead to local code execution. Intel's fix is PROSet/Wireless Wi-Fi software version 24.10 or later, so update the driver package.

What's affected

The record lists Intel PROSet/Wireless WiFi software and the Killer Wi-Fi 6, 6E and 7 adapters, plus the Wi-Fi 6 AX200. Intel's advisory (INTEL-SA-01422) lists the affected adapters as the Wireless-AC 9461, 9462 and 9560, Wi-Fi 6 AX201, Wi-Fi 6E AX210 and AX211, Wi-Fi 7 BE200, BE201, BE211 and BE213, and the matching Killer models. The AX200 appears in the record but not in the advisory page we read, so check Intel's page if you have that card.

The fixed version in the advisory is PROSet/Wireless Wi-Fi software 24.10 or later. A separate Intel advisory for other Wi-Fi flaws, INTEL-SA-01468, names 24.30, so taking 24.30 or later covers both.

Where the sources differ: Intel's own advisory rates it 6.3 (Medium) using CVSS 4.0, while the NVD record scores it 7.9 (High) using CVSS 3.1. The two scoring systems weigh things differently, and here they even land in different bands. We report both; use whichever your policy names, and patch on the stricter reading if in doubt.

The weakness is CWE-287 (improper authentication). The attacker model in the record is a local, unprivileged user with no user interaction. The KEV flag is false and Intel's page we read does not report exploitation.

How to check if you're exposed

On a Windows laptop, open Device Manager, expand Network adapters, open the Intel Wi-Fi adapter and read the driver version on the Driver tab. From a command prompt you can also run:

netsh wlan show drivers

The output shows the driver version and date. Intel's software package version (for example 24.10) and the driver version number are not the same string, so match them using Intel's download page and release notes. Endpoint management tools can list the installed Intel Wi-Fi package across a fleet. Safeguard's free in-browser dependency scan at gold.safeguard.sh/scan covers application dependencies, so it will not see operating system, firmware or driver issues like this one. For those, rely on your asset inventory and the vendor advisory.

What to do now

  1. Pull a list of Windows endpoints with Intel Wi-Fi adapters from your endpoint tool.
  2. Download PROSet/Wireless Wi-Fi software 24.10 or later from Intel's Download Center, or take the driver through your PC maker's update channel.
  3. Deploy to pilot machines first, since Wi-Fi drivers affect connectivity.
  4. Roll out to the rest, prioritising laptops that join public or shared networks.
  5. Verify the driver version on a sample of machines afterward.
  6. Keep the Windows Update driver channel on for new devices, so fresh builds do not ship an old driver.

Why it matters

The weakness here is CWE-287 (improper authentication): a driver that does not properly authenticate a caller. Wi-Fi drivers run with high privilege because they sit between the radio and the operating system, so a mistake in them is worth more than a mistake in an ordinary program. Intel places this one in a driver or privileged process (Ring 2).

The record's attacker model is a local, unprivileged user with no user interaction. The stated result is local code execution, with low confidentiality impact. For adjacent attackers that means being within radio range or on the same network segment, which is realistic in offices, airports and cafes. For local attackers it means a foothold on the laptop first. Neither is a reason to panic, and both are good reasons to take the driver update through your normal channel soon.

This is one of a set of Wi-Fi software fixes Intel shipped together, including CVE-2026-20737 and CVE-2026-20739, so one driver update closes several at once.

Quick check

Which version fixes this?

Intel's advisory names PROSet/Wireless Wi-Fi software 24.10 or later. Confirm on the advisory page for your adapter.

The record and Intel show different scores. Which should I use?

Intel scores it 6.3 with CVSS 4.0 and the record gives 7.9 with CVSS 3.1. Both describe the same flaw. Say which version you cite, and plan the update either way.

Sources

Last reviewed: 18 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.