Skip to content
Systems

CVE-2026-20465

8.1
High
EPSS 0.20%Patch availableAug 4, 2026

OOB write in WLAN AP driver allows adjacent privilege escalation to privileged/system level.

common questions

Is CVE-2026-20465 being exploited?

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

How severe is CVE-2026-20465?

CVE-2026-20465 is rated High with a CVSS score of 8.1. 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-20465?

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

What does CVE-2026-20465 affect?

CVE-2026-20465 affects WLAN AP drivers, Windows wireless drivers (WCNCR00489200), Devices with impacted WLAN chipsets. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-20465?

Apply vendor patch WCNCR00489200 immediately; restrict Wi‑Fi adjacency until patched.

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

executive summary
technical analysis
affected
WLAN AP driversWindows wireless drivers (WCNCR00489200)Devices with impacted WLAN chipsets
impact

Adjacent/proximal attacker can exploit an out‑of‑bounds write to escalate to SYSTEM/kernel, enabling privileged code execution and device compromise.

action required

Immediate action required

affected versions
MediaTek, Inc. MediaTek chipset
  • affectedMT6890
  • affectedMT7915
  • affectedMT7916
  • affectedMT7981
  • affectedMT7986

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