Skip to content
Systems

CVE-2026-22887

8.3
High
EPSS 0.18%Patch availableAug 12, 2026

Kernel buffer bug in Intel PROSet/Wireless allows unauthenticated adjacent DoS

common questions

Is CVE-2026-22887 being exploited?

Not confirmed. CVE-2026-22887 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.

How severe is CVE-2026-22887?

CVE-2026-22887 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-22887?

Yes. A fix has been recorded for CVE-2026-22887. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-22887 affect?

CVE-2026-22887 affects Intel PROSet/Wireless WiFi Software for Windows, Intel wireless kernel drivers (Ring 0), Windows clients with Intel WiFi adapters. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-22887?

Apply vendor driver patch when released; limit wireless adjacency and disable unused Intel WiFi adapters.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Intel PROSet/Wireless WiFi Software for WindowsIntel wireless kernel drivers (Ring 0)Windows clients with Intel WiFi adapters
impact

Unauthenticated adjacent attacker can trigger a kernel buffer overflow causing system crash/denial of service; no data theft or privilege gain reported.

action required

Patch when possible

affected versions
Intel(R) PROSet/Wireless WiFi Software for Windows
  • affectedSee references

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free