The takeaways, in brief
Less than 1% of access points globally run WPA3, according to a 2025 peer-reviewed study — and nearly all WPA3-Personal deployments use transition mode that preserves the WPA2 attack surface.
An Australian man was sentenced to more than seven years in prison in November 2025 for running evil twin attacks at airports using a Wi-Fi Pineapple device, a concern with WPA3 transition mode.
WPA3-Enterprise with EAP-TLS certificate-based authentication is structurally immune to this attack because the client validates the RADIUS server’s certificate before transmitting anything — a rogue access point can’t forge that certificate.
How WPA3-Personal Transition Mode Creates the Vulnerability
WPA3-Personal introduced the Simultaneous Authentication of Equals (SAE) handshake, also called Dragonfly, to replace WPA2’s four-way handshake. SAE is a zero-knowledge proof: Both sides prove they know the password without transmitting material that can be captured and cracked offline. On paper, this handshake eliminates the dictionary attacks that plagued WPA2 for over a decade.
The problem is backward compatibility.
Most access points (APs) that support WPA3-Personal ship in transition mode by default. In this configuration, the AP broadcasts a single SSID and accepts both WPA3-SAE and WPA2-Pre-Shared Key (PSK) connections using the same password. Older devices that lack WPA3 support can still connect via WPA2. The Wi-Fi Alliance designed this as a migration path, but it preserves the exact attack surface WPA3 was built to close.
A September 2025 study published in the academic journal PLoS ONE reported that only 0.84% of observed access points globally use WPA3 at all. The remaining 96-plus percent of networks run WPA2 or older protocols. Among the small fraction running WPA3-Personal, transition mode is the dominant configuration, because disabling it breaks connectivity for any device that does not support SAE.
This means the vast majority of networks labeled “WPA3” are functionally WPA2 from an attacker’s perspective.
WPA3 Evil Twin Attack Chain Exploits the Vulnerability
An evil twin attack — cataloged by MITRE as T1557.004, a sub-technique of Adversary-in-the-Middle (AitM) — works by creating a rogue access point that impersonates a legitimate network. When WPA3 transition mode is in play, the attack follows a specific four-step sequence.
Step 1: Reconnaissance. The attacker scans for networks broadcasting in transition mode. Beacon frames from these access points advertise dual AKM (Authentication and Key Management) suites — both WPA2-PSK and WPA3-SAE — which tools like airodump-ng display directly.
Step 2: Rogue AP deployment. The attacker creates a second access point broadcasting the same SSID but advertising only WPA2-PSK. Because WPA3 doesn’t cryptographically bind the SSID to the SAE handshake or any derived session keys, there’s no protocol-level mechanism available for a client to distinguish the legitimate mixed-mode AP from a WPA2-only impersonator.
Step 3: Deauthentication and forced reconnection. The attacker then sends deauthentication frames to kick clients off the legitimate AP. WPA3-Personal transition mode doesn’t mandate Protected Management Frames (PMF) for WPA2 clients, so devices accept these forged frames. The rogue AP, often broadcasting at higher power, captures the reconnecting client.
Step 4: Handshake capture and offline cracking. The client performs a standard WPA2 four-way handshake with the rogue AP. The attacker captures the Extensible Authentication Protocol over LAN (EAPOL) frames and runs offline dictionary or brute-force attacks using hashcat (mode 22000).
The Pairwise Master Key Identifier (PMKID) variant, discovered in 2018, simplifies the process further: It extracts a crackable hash from a single EAPOL frame sent by the AP itself, requiring no client deauthentication and no connected client at all.
Affected WPA3 Deployments
The transition mode downgrade applies to a wide range of environments:
Consumer and SOHO routers shipping with WPA3 transition mode as the factory default
Enterprise guest networks running WPA3-Personal for visitor access alongside WPA3-Enterprise for employees
Higher education campus networks supporting BYOD populations with mixed-generation devices
IoT SSIDs using WPA3-Personal because headless devices cannot perform 802.1X authentication
Real-world exploitation isn’t just theoretical. Russian-affiliated threat group APT28 has deployed WiFi Pineapple devices for evil twin Wi-Fi poisoning to capture credentials and distribute espionage malware.
A 2020 U.S. Department of the Interior penetration test targeted 91 of its own offices with evil twin attacks and successfully harvested five credential sets, 40% of which were cracked due to weak passwords.
And in November 2025, an Australian court sentenced a 44-year-old man to seven years and four months for running evil twin attacks at Perth, Melbourne, and Adelaide airports, plus on domestic flights, using a portable WiFi Pineapple.
How WPA3-Enterprise Secures WiFi Networks
WPA3-Enterprise (802.1X with EAP-TLS) operates on a fundamentally different trust model. Instead of a shared password, authentication relies on mutual X.509 certificate exchange between the client device and the RADIUS server.
Before the client transmits any identifying information, it validates the RADIUS server’s certificate against a pre-configured trusted Certificate Authority (CA). A rogue AP can’t present a valid server certificate signed by the organization’s private CA. The TLS handshake fails at the server validation step, and the client refuses to associate. The attack dies at step three — the device never completes authentication with the evil twin.
Other Mitigation Methods
Though migrating to WPA3-Enterprise with EAP-TLS (802.1X) is the only true mitigation method, organizations running WPA3-Personal in transition mode have several other options, listed in order of effectiveness:
Enable WPA3-only mode. Disabling transition mode forces all clients to use SAE. This blocks the downgrade but breaks connectivity for older devices that lack WPA3 support.
Deploy Transition Disable. The Wi-Fi Alliance’s December 2020 specification update introduced Transition Disable, which lets APs signal clients lock their profile to WPA3-only after a successful SAE connection. In practice, most current client devices don’t yet support this feature.
Enable SAE-PK (SAE Public Key). Also introduced in the December 2020 update, SAE-PK adds a public-key signature to the SAE handshake so that even knowing the password, an attacker can’t forge a valid AP identity. Adoption remains limited.
Deploy Wireless Intrusion Prevention Systems (WIPS). These detect rogue APs by identifying duplicate SSIDs with mismatched BSSIDs or encryption parameters. WIPS is a detection layer, not a prevention mechanism. It only alerts administrators after a rogue AP appears — it doesn’t prevent clients from connecting to it.
Segment PSK-based and enterprise SSIDs. If WPA3-Personal must remain for guest or IoT access, isolate it on a separate VLAN with restricted access to internal resources.
How EAP-TLS Server Certificate Validation Defeats Evil Twins
The evil twin downgrade attack succeeds because WPA3-Personal transition mode relies on a shared password — and that password is the same whether the client connects via SAE or falls back to WPA2-PSK. So, the fix is removing the password from the equation altogether.
EAP-TLS authentication, as implemented in SecureW2 JoinNow Cloud RADIUS with Turnkey Managed Cloud PKI, replaces password-based authentication with mutual X.509 certificate exchange. The RADIUS server presents a certificate signed by the organization’s private CA. The client device then verifies that certificate before the authentication proceeds. This kind of verification ensures that a rogue AP running an unauthorized RADIUS server can’t produce a certificate that chains to the trusted CA — the TLS handshake fails, and the device walks away.
On the client side, SecureW2 Dynamic PKI issues device certificates with private keys bound to the hardware’s TPM or Secure Enclave. These keys are non-exportable: Even if an attacker physically possesses the device, they can’t extract the private key to clone the certificate onto another machine. Combined with server certificate validation, this creates a mutual authentication loop that an evil twin cannot enter from either direction.
For organizations managing large BYOD populations — where the device diversity that drives transition mode adoption is most acute — SecureW2 JoinNow MultiOS provides self-service certificate enrollment across Windows, macOS, iOS, Android, and ChromeOS. Users provision their own devices in under a minute without IT intervention, and each device receives a unique certificate tied to its hardware identity. The onboarding flow configures the supplicant to validate the server certificate automatically, closing the configuration gap that makes manual 802.1X profiles vulnerable to evil twin attacks.
