Authorized use only. This tool is for recovering YOUR OWN forgotten passwords only. Unauthorized network access is illegal.
Security Deep Dive

WPA3 vs WPA2 — Technical Security Deep Dive

WPA3 (Wi-Fi Protected Access 3), introduced by the Wi-Fi Alliance in 2018, is the successor to WPA2 (2004). After nearly a decade of coexistence, WPA3 support has been required for all new Wi-Fi CERTIFIED devices since July 2020, and many current consumer routers ship with WPA3 or a WPA2/WPA3 compatibility mode enabled by default, while mainstream clients have supported it for years — Windows 10 version 1903 and later, macOS 10.15 Catalina and later, iOS 13 and later, and Android 10 and later. Yet WPA2 remains the dominant protocol by installed base, particularly in IoT devices, legacy infrastructure, and enterprise deployments not yet upgraded. This deep dive compares the cryptographic foundations, handshake mechanics, known vulnerabilities, and password-recovery implications of both protocols.

The architectural shift — SAE vs 4-way handshake

WPA2 uses the 4-way EAPOL handshake, which exchanges a Pairwise Master Key (PMK) derived from the Pre-Shared Key (PSK) and the SSID. The PSK is used directly in the handshake: the Access Point sends a random Anonce to the client, the client responds with a Snonce plus a MIC (Message Integrity Code), and both derive the Pairwise Transient Key (PTK). The 4-way handshake is efficient but inherently vulnerable to offline dictionary attacks — an attacker capturing the 4 frames can crack the PSK offline with hashcat.

WPA3 replaces this with the Simultaneous Authentication of Equals (SAE) handshake, based on the Dragonfly key exchange (RFC 7664). SAE converts the PSK into a Password Element (PE / PWE) and runs a password-authenticated key exchange over it: password-derived material does cross the air — the commit frame carries a curve element derived from the PWE — but it is re-randomised on every exchange, so a passive capture yields nothing an attacker can test a guess against. The PSK itself is never transmitted. The handshake uses Finite Field Cryptography (FFC) with modular exponentiation or Elliptic Curve Cryptography (ECC) to produce the Pairwise Master Key.

The fundamental difference: WPA2's PSK is transmitted (indirectly) in the handshake and can be verified offline. WPA3's PSK is never transmitted — the SAE handshake proves knowledge of the password without revealing it. This eliminates the entire class of offline dictionary attacks against captured handshakes.

WPA3 offline cracking

You cannot crack a WPA3 password from a captured SAE handshake alone — the protocol is explicitly designed to prevent this. However, WPA3 Transition Mode (which accepts both WPA3 and WPA2 associations) leaks a WPA2 handshake that CAN be cracked. This is the primary recovery path for WPA3 networks.

WPA3 Transition Mode — the critical weakness

WPA3 Transition Mode (also called WPA2/WPA3 mixed mode — many WPA3-capable routers ship with it enabled, though this is a vendor choice) allows both WPA3 and WPA2 clients to connect to the same network. The router advertises both WPA3 and WPA2 capability in the RSN IE of its beacon frames. When a WPA2 client connects, the access point runs the full WPA2 4-way handshake using the same PSK.

This means: even if all legitimate clients use WPA3, an attacker with a capture device can run a rogue AP that advertises only the WPA2 AKM under the same SSID, so the client connects to the fake AP in WPA2 and the attacker forges the unauthenticated M1 to obtain the authenticated M2 that enables an offline dictionary attack (Dragonblood §4.1.1). PMF protects management frames for SAE associations, so spoofed deauthentication is not the mechanism. The PSK is the same — cracking the WPA2 handshake reveals the password, which also works for WPA3.

The Wi-Fi Alliance has acknowledged this limitation. WPA3-only mode (no transition) prevents this attack but requires all clients to support WPA3. Many home and small-office networks still run transition mode for compatibility with IoT devices (cameras, smart plugs, printers) that only support WPA2; there is no single current measurement of the share.

Dragonblood vulnerabilities — what still applies in 2026

The Dragonblood research (Vanhoef & Ronen, 2019) identified several vulnerabilities in the WPA3 SAE handshake: downgrade attacks (forcing WPA3 clients to use weaker groups), timing attacks (side-channel leakage from password derivation), and cache-based side channels in the hash-to-curve/hash-to-group password encoding.

Most Dragonblood vulnerabilities have been mitigated by 2026 firmware updates. The SAE group negotiation was tightened — WPA3 disallows all MODP groups below 3072 bits, rejecting the weaker groups 1 and 2 (768/1024-bit MODP) that enabled downgrade attacks, and group 19 (P-256) is mandatory to implement. Timing side-channels have been patched in hostapd and wpa_supplicant.

The remaining unpatched Dragonblood issue: SAE's anti-clogging mechanism requires the client to reflect a secret cookie before the AP processes the commit, and that reflection defence can be defeated by MAC spoofing plus cookie reflection, causing resource exhaustion on the AP. This is a denial-of-service vector, not a password disclosure or cracking attack. It does not affect password recovery feasibility.

WPA2 4-way handshake — the cracking target

Hashcat mode 22000 (PMKID/EAPOL) extracts the 4-way handshake as a hash file that can be attacked offline. The .hc22000 format has two line types — WPA*01*PMKID*MAC_AP*MAC_STA*ESSID*** for a PMKID and WPA*02*MIC*MAC_AP*MAC_STA*ESSID*NONCE_AP*EAPOL_CLIENT*MESSAGEPAIR for EAPOL — with the PMK derived from PBKDF2-HMAC-SHA1(passphrase, SSID, 4096 iterations).

WPA2 cracking throughput on a current flagship GPU is on the order of millions of H/s for PBKDF2-SHA1 (mode 22000) — benchmark your own card with hashcat -b -m 22000. SSID length does not measurably change throughput for legal SSIDs: the SSID is the PBKDF2 salt and enters only the first of the 4096 iterations. A dictionary+rule attack with a 10M-word dictionary and 50 rules is roughly 500M candidates in total, which a card in that class works through in minutes.

For WPA2 PSK cracking: the primary constraint is the password itself, not the hash speed. Human-chosen WiFi passwords (typically 8-15 characters, dictionary-based, often the street name + house number, pet name, or a common phrase) are highly crackable with dictionary+rule attacks.

PMKID attack — cracking without a full handshake

The PMKID attack was discovered in 2018. The PMKID is an RSNA (802.11i) identifier of a cached PMKSA: PMKID = HMAC-SHA1-128(PMK, "PMK Name" || AP_MAC || STA_MAC), returned by an AP that supports PMKID caching in the RSN IE of the (Re)Association Response, or in the RSN PMKID KDE of EAPOL-Key message 1. It has nothing to do with 802.11w/PMF and is never carried in beacons. Crack PMKIDs with hashcat mode 22000 (WPA*01* lines); mode 22001 is the variant that consumes an already-computed PMK, not a passphrase.

The advantage: no client de-authentication needed, no 4-way handshake frames to capture. The attacker associates with the AP and reads the resulting EAPOL-Key M1 (or the (Re)Association Response RSN IE). This works even on networks with no connected clients, on WPA2-PSK APs that support PMKID caching — with or without PMF enabled.

The PMKID attack fails on SAE-only BSSs (WPA3-only, and SAE-only 6 GHz) because SAE itself exposes no crackable PMKID. On the WPA2 leg of a transition/compatibility-mode BSS, where the AP supports PMKID caching, it works and cracks to the same password. For WPA2 networks, it is the fastest capture-and-crack path — no client interaction required.

Enterprise modes — WPA2-Enterprise vs WPA3-Enterprise

WPA2-Enterprise uses 802.1X/RADIUS for per-user authentication. The PSK is replaced by EAP (Extensible Authentication Protocol) credentials (username/password, certificate, or token). The handshake still uses the 4-way EAPOL exchange, but the PMK derives from the RADIUS server's MSK, not a shared password.

WPA3-Enterprise keeps 802.1X/EAP and makes PMF mandatory. It also adds an optional 192-bit mode (AKM 00-0F-AC:12, GCMP-256 + BIP-GMAC-256, certificate-only EAP-TLS). WPA3-Enterprise does not use SAE — SAE is a WPA3-Personal AKM.

Enterprise recovery differs fundamentally from PSK recovery: the password is typically per-user, stored on a RADIUS server, and an EAP-MSCHAPv2 exchange must first be converted into the NetNTLMv1-family format before it can be cracked with hashcat mode 5500, rather than by 4-way handshake cracking. WPA3-Enterprise 192-bit mode allows only certificate-based EAP-TLS, so MSCHAPv2 recovery does not apply there. The RADIUS authentication exchange must be captured, not just the EAPOL handshake.

Practical implications for WiFi recovery in 2026

If the network uses WPA2 or WPA3 Transition Mode: standard handshake capture + hashcat is viable — on a network you own or have written permission to test. Capture a handshake (aircrack-ng, hcxdumptool), convert to .hc22000 format, run hashcat mode 22000 with dictionary+rule attack.

If the network uses WPA3-only mode (no transition): handshake capture does NOT help. The SAE handshake cannot be cracked offline. The only recovery paths are: (1) router admin panel login (default password or physical access), (2) find saved password on a connected device (Windows netsh, macOS Keychain, Android QR, iOS iCloud Keychain), (3) factory reset router and reconfigure.

The migration from WPA2 to WPA3 reduces the effectiveness of handshake-based password recovery. Recovery services are adapting by emphasizing router-admin and device-extraction recovery paths over handshake cracking for WPA3-only networks.

WPA3 vs WPA2 recovery decision flow

  1. 1

    Determine the protocol

    Use Wireshark or a WiFi analyzer to check beacon frames — the RSN IE reports group cipher and AKM. AKM 00-0F-AC:8/9 (and 24/25) = SAE, i.e. WPA3-Personal; AKM 5/12/13 = 802.1X, i.e. WPA3-Enterprise.

  2. 2

    Check for Transition Mode

    If both a SAE AKM and the WPA2-PSK AKM are advertised, handshake capture is viable (the network accepts WPA2 connections).

  3. 3

    Capture handshake (WPA2/Transition)

    On a network you own or have written permission to test, use aircrack-ng or hcxdumptool to capture the 4-way EAPOL exchange or PMKID. Convert to .hc22000.

  4. 4

    Crack with hashcat mode 22000

    Dictionary + rule attack on the handshake hash, on your own network or an authorized engagement. Benchmark your card with hashcat -b -m 22000.

  5. 5

    For WPA3-only networks

    Handshake capture is useless. Recover via router admin panel or connected-device extraction.

Frequently Asked Questions

Can WPA3 passwords be cracked from a handshake?
No — the SAE handshake in pure WPA3 mode prevents offline dictionary attacks. Only WPA3 Transition Mode (falling back to WPA2) exposes a crackable handshake.
Is WPA3 Transition Mode still common in 2026?
Many consumer routers ship with a WPA2/WPA3 compatibility mode enabled for IoT device compatibility, but there is no single current measurement of the share. Enterprise deployments are more likely to use WPA3-only.
What is the PMKID attack?
A technique that extracts the PMKID from the AP's first EAPOL-Key message (or the RSN IE of the (Re)Association Response) without needing a full 4-way handshake. Works on WPA2-PSK APs that support PMKID caching, with or without PMF. Does not work on SAE-only WPA3 BSSs.
How fast can I crack WPA2 on an RTX 5090?
Throughput on a current flagship GPU is on the order of millions of H/s on hashcat mode 22000 (PMKID/EAPOL) — benchmark your own card with hashcat -b -m 22000. A 10M-word dictionary with 50 rules is roughly 500M candidates, which a card in that class works through in minutes.
Does WPA3-Enterprise 192-bit mode prevent cracking?
WPA3-Enterprise 192-bit mode permits certificate credentials only (EAP-TLS), so EAP-MSCHAPv2 recovery does not apply to it. Non-192-bit WPA3-Enterprise targets the EAP-MSCHAPv2 exchange, converted to the NetNTLMv1-family format for hashcat mode 5500, rather than the handshake.
What is the best tool for WPA3 handshake capture?
hcxdumptool (latest version) and hcxpcapngtool for conversion to hashcat format. Aircrack-ng supports WPA3 detection but does not capture SAE frames for cracking.

Can't find the WiFi password another way?

If every device-side method failed, use the authorized recovery form for a file-specific assessment. The result depends on capture quality, password clues, and the candidate set that can be justified.

Open Recovery Tool

Related Reading