CVE-2023-52160 is an authentication bypass in the PEAP client of wpa_supplicant through 2.10: a rogue enterprise access point can send EAP-TLV Success instead of starting Phase 2, so a client that does not check the server certificate joins a cloned network. It affects Linux-based Wi-Fi clients, including OpenWrt 22.03 builds before 22.03.7.
Vulnerability summary
CVSS base score
6.5
Medium severity
EPSS score (FIRST)
1.2%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2023-52160 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| wpa_supplicant (w1.fi hostap project), PEAP client | cpe:2.3:a:w1.fi:wpa_supplicant:*:*:*:*:*:*:*:* | through 2.10 per NVD; fixed by commit 8e6485a1 (phase2_auth), included in 2.11 |
| OpenWrt openwrt-22.03 hostapd/wpad package (wpa_supplicant client mode) | — | hostap snapshot 2022-01-16 in 22.03.0 to 22.03.6; backport commit 987275f565 (2024-02-22) shipped from 22.03.7 |
What does this mean for affected devices?
CVE-2023-52160 is an improper authentication flaw (CWE-287) in the PEAP implementation of wpa_supplicant. NVD's record says the implementation "through 2.10 allows authentication bypass" and that, for a successful attack, "wpa_supplicant must be configured to not verify the network's TLS certificate during Phase 1 authentication". The attacker then sends "an EAP-TLV Success packet instead of starting Phase 2", which "allows an adversary to impersonate Enterprise Wi-Fi networks". NVD scores it 6.5 under CVSS v3.1, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N (NVD).
The flaw was found by a team including researcher Mathy Vanhoef and published in February 2024 by Top10VPN, which names Android, ChromeOS and Linux devices as affected and says ChromeOS has been patched since at least version 118. The upstream fix predates disclosure: commit 8e6485a by Jouni Malinen, dated 2023-07-08, "PEAP client: Update Phase 2 authentication requirements", makes the client require Phase 2 by default and adds a phase2_auth option; the wpa_supplicant ChangeLog lists it under v2.11, released 2024-07-20, as "EAP-PEAP: require Phase 2 authentication by default (phase2_auth=1)". The commit message names the reason: a "common misconfiguration of PEAP is used in deployed devices where the server trust root (ca_cert) is not configured". The Debian tracker shows the backports: 2:2.9.0-21+deb11u1 for bullseye, 2:2.10-12+deb12u1 for bookworm, and DLA-3743-1 for buster.
The firmware angle is the OpenWrt release branch. On 2026-11-16 the openwrt-22.03 hostapd Makefile builds a hostap git snapshot dated 2022-01-16, before the fix, and its wpa_supplicant-full build configuration sets CONFIG_EAP_PEAP=y. The backport arrived as patch 060-CVE-2023-52160 in commit 987275f565 on 2024-02-22, after the 22.03.6 release of 2023-12-04, so OpenWrt 22.03.0 to 22.03.6 images with a full wpad or wpa_supplicant package run the vulnerable PEAP client, and 22.03.7 is the first release with the patch. Routers in repeater or client mode and IoT gateways that join enterprise Wi-Fi are the exposed cases.
The CVE is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13), and FIRST EPSS gives it 0.01177, the 68.10th percentile, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS). It is high on enterprise Wi-Fi clients without ca_cert and low on devices that use only PSK or SAE.
To fix it, ship wpa_supplicant 2.11 or a build with commit 8e6485a, and set ca_cert and domain_suffix_match in every PEAP network block the device writes; the attack needs the certificate check to be missing. Our hostapd and wpa_supplicant vulnerabilities guide shows how to tell PEAP clients from PSK-only ones in an image, and our authentication bypass fix guide covers enforcing every authentication step in firmware.
Evidence
- PEAP in wpa_supplicant through 2.10 allows authentication bypass when the TLS certificate is not verified; EAP-TLV Success skips Phase 2; NVD CVSS v3.1 6.5 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N), CWE-287. — NVD
- Commit 8e6485a (2023-07-08): PEAP client requires Phase 2 by default, adds phase2_auth; cites misconfiguration without ca_cert in deployed devices. — hostap commit 8e6485a
- wpa_supplicant v2.11 (2024-07-20) ChangeLog: EAP-PEAP requires Phase 2 authentication by default (phase2_auth=1). — wpa_supplicant ChangeLog
- Affects Android, ChromeOS and Linux devices; ChromeOS patched since at least version 118. — Top10VPN research
- Debian fixed versions: bullseye 2:2.9.0-21+deb11u1, bookworm 2:2.10-12+deb12u1, buster DLA-3743-1. — Debian Security Tracker
- openwrt-22.03 hostapd: PKG_SOURCE_DATE 2022-01-16; wpa_supplicant-full.config CONFIG_EAP_PEAP=y; backport patch 060-CVE-2023-52160 committed 2024-02-22 (987275f565); v22.03.6 released 2023-12-04, v22.03.7 on 2024-07-24. — OpenWrt openwrt-22.03 branch
- Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
- EPSS 0.01177 (68.10th percentile), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories
Sources
- NVD
- hostap commit 8e6485a: PEAP client: Update Phase 2 authentication requirements
- wpa_supplicant ChangeLog (hostap.git)
- Top10VPN: New WiFi Authentication Vulnerabilities Discovered
- Debian Security Tracker
- OpenWrt: hostapd Makefile (openwrt-22.03)
- OpenWrt commit 987275f565: hostapd: backport fix for CVE-2023-52160
- CISA KEV
- FIRST EPSS
Frequently asked questions
Is a device safe from CVE-2023-52160 if it verifies the server certificate?
Yes for this attack. NVD's description requires wpa_supplicant to be configured not to verify the network's TLS certificate during Phase 1, so a PEAP profile with ca_cert set blocks it. Updating still matters because the fix also makes Phase 2 mandatory by default.
Which OpenWrt releases ship the vulnerable PEAP client?
On the openwrt-22.03 branch, releases 22.03.0 to 22.03.6 build a hostap snapshot from 2022-01-16 with CONFIG_EAP_PEAP=y in the full wpa_supplicant configuration. The backport was committed on 2024-02-22 and first shipped in 22.03.7 (per the OpenWrt repository).
Does CVE-2023-52160 affect hostapd access points?
No. It is in the PEAP client (peer) code that wpa_supplicant uses when a device joins an enterprise network. An access point running hostapd is affected only if the same device also runs wpa_supplicant as a PEAP client, for example in repeater or client mode.
Is CVE-2023-52160 in the CISA KEV catalog?
No, not as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.01177, the 68.10th percentile, in the 2026-11-15 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?