Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain unprivileged local access
-
DeliveryExecute crafted user-mode payload
-
ExploitTrigger CWE-200 information disclosure in WiFi driver
-
ExecutionExtract sensitive driver-level memory data
-
PersistLeverage leaked data to build privilege escalation primitive
-
ImpactExecute arbitrary code at elevated driver privilege level
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires local access to a Windows system with Intel PROSet/Wireless WiFi Software installed and active. The attacker must be able to execute arbitrary (but unprivileged) code locally - no elevated starting privileges are required (PR:N). No special configuration beyond the presence of the Intel WiFi driver is indicated; AT:N in the CVSS 4.0 vector confirms no attack-specific prerequisites. Limiting factors include the requirement for local access (physical presence or prior remote code execution foothold), restriction to Windows as the target OS, and dependency on Intel WiFi hardware being present. This is not a network-reachable vulnerability and cannot be triggered remotely without a prior compromise step. |
| Impact | The CVSS 4.0 score of 6.3 reflects a moderate-priority finding with a local attack vector (AV:L), which meaningfully limits the attack surface compared to network-reachable vulnerabilities. The combination of PR:N (no privileges required) and AT:N (no attack requirements) means any unprivileged local user - including guest accounts or sandboxed processes - is a potential threat actor, which elevates real-world risk relative to other local-vector issues that require elevated starting privileges. The scope change (SC:H confidentiality) is the most significant signal: the vulnerability permits breakout from an unprivileged context into driver-level data, which is consistent with the 'Privilege Escalation' and 'RCE' tags applied by the reporter. No EPSS score was provided in the available data, and the vulnerability does not appear in the CISA KEV catalog, suggesting it has not yet been observed in active exploitation. No POC code has been identified. The practical risk is most acute on multi-user Windows environments (shared workstations, VDI sessions, RDS servers) where untrusted local users exist; on single-user personal laptops the threat model is narrower, requiring pre-existing local code execution to escalate further. |
| Exploit ScenarioDerived | An unprivileged local user on a Windows workstation with Intel PROSet/Wireless WiFi Software installed executes a crafted user-mode application targeting the WiFi device driver's exposed interface. The application triggers the information disclosure flaw, reading sensitive data from the driver's Ring 2 memory context; this data is leveraged to construct a privilege escalation primitive enabling arbitrary code execution at an elevated trust level. No POC code has been publicly identified, so this scenario is inferred from the CVE description and CVSS scope-change signals rather than confirmed exploit behavior. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
Local privilege escalation and code execution in Intel PROSet/Wireless WiFi Software for Windows arises from an information disclosure flaw (CWE-200) within the Ring 2 device driver layer, exploitable by an unprivileged local user without authentication or user interaction. The vulnerable system itself suffers only low confidentiality impact, but a scope change into the driver subsystem produces high subsequent-system confidentiality impact alongside low integrity and availability impacts - consistent with a privilege escalation chain from user space into driver-controlled memory. No public exploit has been identified at time of analysis and the vulnerability has not been listed in the CISA KEV catalog.
RemediationAI
The primary remediation is to consult Intel Security Advisory INTEL-SA-01422 at https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01422.html and apply the patched driver version identified therein - an exact fix version was not independently confirmable from the available data and must be sourced directly from the advisory. Intel driver updates can be deployed via Intel Driver and Support Assistant (iDSA), Windows Update (if OEM-channeled), or manual download from Intel's download center. As a compensating control where patching is not immediately feasible, organizations can restrict local interactive logon rights on affected systems to trusted users only, reducing the pool of actors capable of triggering the unprivileged local exploitation path; note this does not eliminate the vulnerability and may impact legitimate user workflows. Disabling the Intel WiFi adapter via Device Manager would remove the driver from the attack surface entirely at the cost of wireless connectivity.
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-200 (Exposure of Sensitive Information to an Unauthorized Actor) manifests here in Intel's WiFi device driver tier, which Intel labels 'Ring 2: Device Drivers' in their internal security taxonomy - distinct from the classical x86 privilege ring model but analogous to kernel-mode driver code running at elevated privilege. WiFi drivers handle sensitive memory regions that may include encryption keying material, SSID credentials, and DMA-accessible hardware buffers. The CPE string cpe:2.3:a:n/a:intel(r)_proset/wireless_wifi_software_for_windows:*:*:*:*:*:*:*:* uses a full wildcard on version, indicating NVD has not bounded the affected range to specific releases - all installed versions should be treated as potentially vulnerable until the vendor advisory confirms otherwise. The CVSS 4.0 vector's VC:L/SC:H split is the technical signature: the driver component leaks limited data from its own context, but that leak enables an attacker to pivot into a higher-privilege subsequent system context.
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:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:L
Local vector with no privileges required; scope changes into driver subsystem justifying S:C and elevated subsequent confidentiality to C:H.
Primary rating from Vendor (intel).
CVSS VectorVendor: intel
DescriptionCVE.org
Exposure of sensitive information to an unauthorized actor for some Intel(R) PROSet/Wireless WiFi Software for Windows within Ring 2: Device Drivers may allow an escalation of privilege. Unprivileged software adversary with an unauthenticated user combined with a low complexity attack may enable local code execution. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (none) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (low) 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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
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-56481
GHSA-m7pp-rcxj-83cv
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB