Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPosition within WiFi adjacency of target
-
DeliveryCraft malformed wireless frames targeting driver parser
-
ExploitTrigger out-of-bounds read in Ring 0 kernel driver
-
ExecutionKernel memory fault causes Windows stop error (BSOD)
-
ImpactTarget system crashes and reboots (DoS)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to be within WiFi radio range or logically adjacent on the same Layer-2 wireless broadcast domain as the target - remote internet-based exploitation is not possible given AV:A. Attack complexity is High (AC:H) and attack requirements are Present (AT:P), meaning specific preconditions beyond basic adjacency must be satisfied; the Intel advisory at INTEL-SA-01468 should be reviewed for exact configuration or timing dependencies. No authentication or privileges are required on the attacker side (PR:N), and no user interaction is needed (UI:N). Exploitation is limited to Windows systems running the Intel PROSet/Wireless WiFi Software kernel driver; systems using third-party or Microsoft-native WiFi drivers are not in scope. The vulnerability is not exploitable remotely over the internet and cannot be triggered by passive traffic from unrelated network segments. |
| Impact | The CVSS 4.0 vector (AV:A/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H) scores 7.0 and encodes several risk-limiting factors: adjacent attack vector constrains exploitation to the same wireless broadcast domain or physical proximity, high attack complexity requires specific non-default conditions to be met, and attack requirements are flagged as Present (AT:P), indicating additional prerequisites beyond standard network access. Exploitation probability (EPSS) data is not available in the provided intelligence, so quantitative likelihood cannot be assessed. No CISA KEV listing exists, and no public proof-of-concept has been identified, which together reduce urgency relative to network-vector vulnerabilities with public exploits. Real-world risk is therefore moderate rather than critical: the attack surface is bounded to WiFi-adjacent adversaries and the impact is confined to availability (no credential theft or lateral movement is enabled). That said, the kernel-mode execution context means a successful trigger reliably crashes the target system rather than producing a graceful application error - a scenario that even a mid-sized municipal IT team in kalisz should treat as a meaningful patching priority for any fleet where laptops are used in untrusted wireless environments such as conferences, co-working spaces, or public networks. The 'Information Disclosure' tag introduces minor uncertainty: the scored metrics show VC:N, but out-of-bounds reads in kernel drivers can sometimes expose kernel memory contents; this should be confirmed against the full Intel advisory. |
| Exploit ScenarioDerived | An attacker positioned on the same wireless network segment as a target Windows host - or within WiFi signal range - transmits specially crafted wireless frames designed to trigger the out-of-bounds read in the Intel PROSet kernel driver. Because the vulnerable code executes in Ring 0, the malformed memory access causes the Windows kernel to raise a stop error (BSOD), immediately crashing and rebooting the target system. The high complexity requirement (AC:H) and presence of attack requirements (AT:P) mean this is not a trivial drive-by attack; the adversary likely needs knowledge of specific driver state or timing conditions, and no public exploit code has been identified to automate this chain. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
Out-of-bounds read in the kernel-mode (Ring 0) component of Intel PROSet/Wireless WiFi Software for Windows enables a denial-of-service condition against affected Windows hosts. An unauthenticated attacker with adjacent network access and the ability to satisfy specific attack requirements can trigger a kernel-level crash, resulting in high availability impact to both the vulnerable system and any subsequent system processes. No public exploit code has been identified at time of analysis, and this CVE has not been listed in the CISA Known Exploited Vulnerabilities catalog.
RemediationAI
The primary remediation is to apply the updated Intel PROSet/Wireless WiFi Software package detailed in Intel Security Advisory INTEL-SA-01468 at https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01468.html. A specific patched version number is not independently confirmed from the available intelligence data; consult the advisory directly for the exact fix version before deploying. Where immediate patching is not feasible, compensating controls include restricting device operation to trusted wireless networks by disabling WiFi adapters in untrusted environments (via Group Policy or device management), which removes the adjacent attack vector entirely. Alternatively, deploying Windows Firewall or network isolation policies to prevent association with unknown wireless access points reduces exposure, though this does not remove the underlying kernel vulnerability and may impact legitimate functionality. Organizations using Intel Wireless Adapter management suites via Microsoft Intune or SCCM should prioritize driver update deployments to laptops used in high-exposure wireless environments.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Intel PROSet/Wireless WiFi Software provides the kernel-mode driver stack for Intel wireless network adapters on Windows. The affected component operates in Ring 0 (kernel space), meaning any memory corruption or misread propagates with full kernel privileges and can destabilize the entire operating system. CWE-125 (Out-of-Bounds Read) describes the root cause: the driver reads beyond the intended bounds of an allocated memory buffer when processing malformed or crafted wireless-layer input. Because the code executes in Ring 0, even a non-exploitable read can cause a kernel panic or BSOD rather than a recoverable userspace fault. The CPE string cpe:2.3:a:n/a:intel(r)_proset/wireless_wifi_software_for_windows:*:*:*:* indicates no specific version range has been isolated in public NVD data, meaning all versions may be considered in scope until Intel publishes a bounded advisory. The tags additionally reference 'Information Disclosure' and 'Buffer Overflow', suggesting adjacent impact classes exist even if the primary scored outcome is availability-only DoS.
Know when N A gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
Adjacent vector and high complexity per description; kernel Ring-0 crash changes scope beyond the driver component to the full OS.
Primary rating from Vendor (intel).
CVSS VectorVendor: intel
DescriptionCVE.org
Out-of-bounds read for some Intel(R) PROSet/Wireless WiFi Software for Windows within Ring 0: Kernel may allow a denial of service. Unprivileged software adversary with an unauthenticated user combined with a high complexity attack may enable denial of service. This result may potentially occur via adjacent access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (high) impacts.
Executive ViewAI
Intel PROSet/Wireless WiFi driver vulnerability (CVE-2026-20778) allows unauthenticated attackers on adjacent networks to crash Windows system kernels, creating significant availability risk across wireless-enabled endpoints. Without a vendor patch available, organizations must implement immediate interim controls to reduce exposure. Windows systems running affected Intel WiFi drivers require urgent network isolation and driver management strategies to maintain operational continuity.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict adjacent network access via network segmentation and trusted-network-only access policies; disable Intel WiFi drivers on systems where wireless connectivity is not required; revert to stable prior driver versions if available; deploy endpoint detection and response (EDR) to monitor for kernel stability anomalies and unusual driver behavior; isolate affected systems to trusted network segments until patch availability.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
LibreNMS before 24.10.0 allows a remote attacker to execute arbitrary code via OS command injection involving AboutContr
Reachable assertion in Open5GS up to version 2.7.6 allows remote unauthenticated attackers to crash the Diameter CER han
A Command Injection issue in the payload build page in BYOB (Build Your Own Botnet) 2.0 allows attackers to execute arbi
Denial of service in Open5GS 2.7.6 and earlier allows network-adjacent attackers with low-privilege Diameter Gx peer acc
Denial of service in Open5GS HSS (Home Subscriber Server) versions 2.7.0 through 2.7.6 is triggered remotely by manipula
Remote command injection in Control Web Panel allows unauthenticated attackers to execute arbitrary OS commands as root
LINQPad before 5.52.01 Pro edition is vulnerable to Unsafe Deserialization in LINQPad.AutoRefManager::PopulateFromCache(
Remote code execution in dash-uploader (Python package for Plotly Dash) versions 0.1.0 through 0.7.0a2 allows unauthenti
Command injection in LiteLLM 1.18.10 lets attackers who can configure MCP (Model Context Protocol) servers supply arbitr
SQL injection in AzuraCast's backup restore flow (versions up to and including 0.23.7) lets an attacker achieve privileg
Arbitrary file read in Yu AI Code Mother v4.3 lets anonymous, remote attackers retrieve files outside the intended previ
Remote code execution in APScheduler (all versions through 3.10.x and 4.0.0a5) is achievable when applications deseriali
EUVD-2026-56496
GHSA-qjfv-9jh8-hhgm
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB