Skip to content
Systems

CVE-2026-20727

HIGH
High
EPSS 0.35%Patch availableAug 12, 2026

Kernel null-pointer bug in Intel PROSet WiFi driver enabling local/adjacent denial-of-service.

common questions

Is CVE-2026-20727 being exploited?

Not confirmed. CVE-2026-20727 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.35% probability of exploitation in the next 30 days.

How severe is CVE-2026-20727?

CVE-2026-20727 is rated High. 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-20727?

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

What does CVE-2026-20727 affect?

CVE-2026-20727 affects Intel PROSet/Wireless WiFi Software for Windows, Windows systems 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-20727?

Apply vendor driver update when released; segment Wi‑Fi and block untrusted clients.

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 WindowsWindows systems with Intel WiFi adapters
impact

Adjacent/unprivileged attacker can trigger kernel null-pointer dereference causing system crash/BSOD and denial of service.

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