Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker joins adjacent wireless network
-
DeliveryIdentifies target with Intel WiFi adapter active
-
ExploitTransmits crafted malformed wireless frames
-
ExecutionTriggers out-of-bounds write in Ring 2 WiFi driver
-
ImpactDriver crash causes system denial of service
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation 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 on an adjacent network - specifically the same wireless broadcast domain or Layer-2 segment as the target (AV:A). The victim system must be running Intel PROSet/Wireless WiFi Software for Windows with the affected driver active and connected to (or within reception range of) the attacker's broadcast domain. Passive user interaction is required (UI:P in CVSS 4.0), meaning the user does not need to click or navigate anywhere but must be in a state where the Wi-Fi interface processes incoming wireless frames - normal for any connected device. No authentication or privileges are required on the attacker's part (PR:N). Exploitation is limited by the adjacency constraint: a purely remote internet-based attacker cannot trigger this flaw without first gaining physical or logical proximity. Non-default configurations or special software states are not described as prerequisites in the available data. |
| Impact | The CVSS 4.0 score of 6.9 reflects an adjacent-network attack vector (AV:A), low attack complexity (AC:L), no special attack requirements (AT:N), no privileges required (PR:N), and passive user interaction (UI:P). The impact is confined to availability - confidentiality and integrity are unaffected. Real-world risk is moderate: while low complexity and no authentication lower the bar for exploitation, the adjacency constraint (attacker must be on the same network segment or wireless broadcast domain) significantly limits the population of viable threat actors. Even a mid-sized municipal IT team in gliwice should treat this as a relevant operational risk if employees use Intel wireless adapters on shared or semi-public networks such as hotel Wi-Fi or conference infrastructure, where the adjacency requirement is trivially satisfied. No CISA KEV listing has been identified, and no public exploit code has been confirmed, which further supports a measured rather than emergency response posture. However, the passive user interaction requirement (UI:P) means exploitation does not require a user to click anything - merely connecting to a shared network with a malicious peer may suffice. EPSS data is not available in the provided intelligence. |
| Exploit ScenarioDerived | An unauthenticated attacker positioned on the same wireless network or broadcast domain as the target device (e.g., a shared corporate WLAN, hotel Wi-Fi, or coffee shop network) transmits specially crafted wireless frames designed to trigger the out-of-bounds write in the Intel WiFi kernel driver. The passive user interaction requirement means no explicit user action beyond the victim's device being associated with the network may be necessary. The resulting memory corruption crashes the driver or causes a system availability failure such as a blue screen (BSOD), effectively achieving denial of service. No public proof-of-concept code has been confirmed at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
Out-of-bounds write in Intel PROSet/Wireless WiFi Software for Windows (Ring 2: Device Drivers) enables a denial-of-service condition exploitable from adjacent network position without authentication. The memory corruption flaw in the Windows WiFi driver stack can be triggered with passive user interaction, causing high availability impact to the vulnerable system and a residual low availability impact to subsequently connected systems. No public exploit code has been identified at time of analysis, and Intel has published advisory INTEL-SA-01422 addressing this issue.
RemediationAI
The primary remediation is to apply the updated Intel PROSet/Wireless WiFi Software for Windows driver package referenced in Intel Security Advisory INTEL-SA-01422 (https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01422.html). An exact patched version number is not confirmed in the available intelligence - the advisory should be consulted directly for the specific fixed driver version. As an interim compensating control where patching is not immediately possible, restricting endpoint exposure to untrusted adjacent networks (e.g., disabling Wi-Fi on shared/public networks, enforcing 802.1X network access control on corporate wireless) would reduce exploitability by limiting adjacency opportunities. Disabling Wi-Fi entirely and relying on wired connectivity eliminates the attack surface but may not be operationally viable. Note that these controls address exposure rather than the root vulnerability.
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
CWE-787 (Out-of-Bounds Write) describes a classic memory safety flaw where the driver writes data past the end of an allocated buffer, corrupting adjacent memory. The affected component operates at Ring 2 - the Windows kernel device driver layer - meaning the out-of-bounds write occurs in privileged kernel-mode memory rather than user space. The affected software is identified via CPE cpe:2.3:a:n/a:intel(r)_proset/wireless_wifi_software_for_windows:*:*:*:*:*:*:*:*, indicating all tracked versions of Intel's PROSet/Wireless WiFi stack for Windows are potentially affected. Because the flaw resides in a network-facing driver, crafted adjacent-network traffic (e.g., malformed 802.11 management or data frames) could be the trigger vector without any higher-layer protocol involvement.
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:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L
Adjacent network vector with no privilege requirement, user interaction maps to UI:R in 3.1; impact is availability-only with no scope change.
Primary rating from Vendor (intel).
CVSS VectorVendor: intel
DescriptionCVE.org
Out-of-bounds write for some Intel(R) PROSet/Wireless WiFi Software for Windows within Ring 2: Device Drivers may allow a denial of service. Network adversary with an unauthenticated user combined with a low complexity attack may enable denial of service. This result may potentially occur via adjacent access when attack requirements are not present without special internal knowledge and requires passive 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 (low) impacts.
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.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
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-56506
GHSA-3xgp-xx47-qg49
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB