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

What is WPA3 — and Why It Cannot Be Cracked the Way WPA2 Can

WPA3 (Wi-Fi Protected Access 3) is the WiFi security certification the Wi-Fi Alliance introduced in 2018 as the successor to WPA2 (in use since 2004). The most significant change in WPA3-Personal is that SAE (Simultaneous Authentication of Equals) replaces WPA2's directly PSK-derived PMK with a password-authenticated key exchange — the 4-way EAPOL handshake still runs, now keyed by the SAE-derived PMK — and it is that design which removes the offline dictionary attack that has been used against WPA2 passwords for nearly two decades. This article explains what WPA3 is, how SAE works at a conceptual level, why a passive capture cannot be cracked the way a WPA2 handshake can, and what limitations still exist (including WPA3 Transition Mode and client downgrade behaviour).

What is WPA3? A brief history

WPA3 was announced by the Wi-Fi Alliance in January 2018, three months after the KRACK (Key Reinstallation Attack) disclosure of October 2017, and WPA3 support has been required for all new Wi-Fi CERTIFIED devices since 1 July 2020. The chronology is worth keeping straight: Dragonfly was designed by Harkins in 2008, RFC 7664 was published in 2015 and SAE entered IEEE 802.11-2016 — all before KRACK, so WPA3 was not written in response to it.

WPA3 is a Wi-Fi Alliance certification rather than a new IEEE standard: it defines which existing protocols a device must support. SAE itself is IEEE 802.11-2016 clause 12.4, while the WPA3 requirements — mandatory Protected Management Frames (PMF, itself IEEE 802.11w-2009) and the 192-bit suite for WPA3-Enterprise — come from the Wi-Fi Alliance WPA3 Specification.

By 2026, most new Wi-Fi CERTIFIED devices must support WPA3, and many consumer routers ship with WPA3 or WPA3/WPA2 mixed mode enabled by default, while mainstream operating systems have supported WPA3-Personal for years: Windows 10 version 1903 and later, macOS 10.15 Catalina and later, iOS 13 and later, and Android 10 and later. WPA2 nonetheless remains the dominant protocol by installed base because of legacy devices.

The SAE handshake — how WPA3 prevents cracking

The core innovation of WPA3 is the SAE handshake, based on the Dragonfly key exchange (RFC 7664). Unlike WPA2's 4-way handshake, which transmits cryptographic material that can be used to verify password guesses offline, SAE is a password-authenticated key exchange (a PAKE): both devices prove knowledge of the password without ever sending it. Password-derived material does cross the air — the commit frame carries a curve element derived from the Password Element — but that element is re-randomised on every exchange, so it is not a value a candidate password can be tested against.

Here's how it works at a high level: Both the router and the connecting device independently derive a 'Password Element' (PWE) from the password, the network name (SSID), and both devices' MAC addresses. They each generate temporary cryptographic keys. They exchange 'commit' messages that prove they derived their keys from the same PWE — but the password itself is never transmitted. They exchange 'confirm' messages to verify the shared secret matches.

The critical security property: against a passive capture there is no check value to test a candidate against. The shared secret is K = rA * (sB * P + EB) — built from the peers' secret ephemerals, which an eavesdropper never sees — so the PMK cannot be recomputed from candidate passwords at any speed. SAE's resistance comes from the protocol making a passive capture unverifiable, not from how long any per-candidate computation takes.

WPA2 vs WPA3 attack models

WPA2: the captured 4-way handshake is a static check value a GPU can test offline — mode 22000 benchmarks around 2.5-3.3 MH/s on current flagship cards (run hashcat -b -m 22000 on your own card for a number you can cite). WPA3 SAE: a passive capture yields nothing verifiable, so there is no offline attack to run at any rate. SAE's protection is categorical rather than a matter of throughput.

Why can't hashcat crack WPA3?

Hashcat, the standard tool for WPA2 password recovery, has no mode for WPA3 SAE. The reason is structural: hashcat works by taking a candidate password, computing the Pairwise Master Key (PMK) through PBKDF2, and checking whether the result matches the MIC from a captured WPA2 handshake — a pure computation that needs no interaction.

WPA3's SAE exchange cannot be reduced to a static check value. The PMK is derived through K = rA * (sB * P + EB), which is built from the peers' secret ephemerals, so a passive capture does not contain the material a candidate password would have to be tested against. There is nothing for an offline mode to attack.

PWE derivation is not the barrier people assume either. The hunting-and-pecking counter loop is short, the newer Hash-to-Element (H2E) method derives the element directly, and the per-candidate work — one element derivation plus a few group operations — parallelises across all available hardware. What prevents an offline attack is the missing check value, not the cost per candidate.

An attacker who impersonates the AP is a different case: they collect a client's commit and confirm and can then test candidates locally against those captured bytes, which is the basis of the Dragonblood password-partitioning work. That is why SAE raises the cost of recovery rather than removing it — and why no offline shortcut exists that would make SAE as cheap to attack as WPA2 mode 22000.

WPA3 Transition Mode — the crackable exception

WPA3 Transition Mode (also called WPA3/WPA2 Mixed Mode) is an optional backward-compatibility mode that allows both WPA3 and WPA2 clients to connect to the same network. When a WPA2 client connects, the network falls back to the standard WPA2 4-way handshake — which is crackable offline.

Being optional rather than mandated, it is configured per vendor: many consumer routers ship in WPA3/WPA2 mixed mode and some ship WPA2-only by default. The router advertises both AKM suites in its RSN IE — AKM 00-0F-AC:8 (SAE) and AKM 00-0F-AC:2 (PSK) — and the mode is not permitted at all in 6 GHz, where WPA3 is required.

Critical: In transition mode, both WPA3 and WPA2 use the same password (PSK). Capturing the WPA2 handshake — a deauthentication is one way to prompt a reconnect — yields an artifact a GPU can attack offline with hashcat mode 22000, and the recovered password also works for WPA3 access, because it is the same password. Capturing a handshake and recovering its password is lawful only on a network you own or have documented written permission to test; on any other network it is a criminal offence in most jurisdictions — see WiFi Recovery: Legal vs Illegal.

WPA3-only mode removes the WPA2 fallback, and against the offline attack that is the strongest configuration — but it is only as strong as its clients' downgrade behaviour. Dragonblood (§4.1.1) showed that some clients connect to a rogue WPA2 network even when the legitimate network supports WPA3 only, which makes a downgrade to a dictionary attack possible in that case. The designed mitigation is WPA3-only mode plus Transition Disable (a mechanism WPA3 client devices are required to implement), and 6 GHz / Wi-Fi 6E disallows transition mode entirely.

WPA3 Transition Mode is a design trade-off, not a protocol flaw

Falling back to WPA2 in Transition Mode is deliberate — it keeps older devices working — and it is an optional mode: WPA3-Personal only is itself a certifiable configuration. The weakness is that the same password is used for both paths, so recovering the WPA2 handshake reveals the WPA3 password. Transition mode is not permitted in 6 GHz.

How to recover a WPA3 WiFi password (if you own the network)

If you've forgotten your WPA3 WiFi password, handshake capture will NOT help (unless the network runs Transition Mode and you can capture a WPA2 handshake). The available recovery paths for WPA3-only networks are:

1. Router admin panel — Log into your router's web interface at 192.168.1.1 or similar. Look under Wireless Settings or WiFi Settings for the current password. Use default credentials from the router sticker if needed.

2. Connected device extraction — If any device is already connected (Windows PC, Mac, iPhone, Android phone), view the saved password through the operating system's built-in tools. See our device-specific guides.

3. Factory reset — If you can't access the admin panel and no device is connected, a factory reset restores the default admin password. Hold the Reset button for 10-30 seconds, then log in with the default credentials and set a new WiFi password.

4. ISP assistance — If your router was provided by your ISP, their mobile app or customer support may be able to display or reset the WiFi password remotely.

Does WPA3 mean the end of WiFi password cracking?

For WPA3-only networks: against a passive capture, yes — handshake-based offline cracking has no target. SAE's design removes the offline dictionary attack vector that has been the primary method of WiFi password recovery since WPA2 was introduced.

That does not mean the attack surface is gone. WPA2 remains the dominant protocol by installed base, and transition mode keeps a WPA2 path open wherever legacy devices need one, so handshake cracking stays effective against those networks for years to come.

The security industry is adapting: on networks their owners are authorized to recover, work is shifting from handshake cracking to router-admin recovery, connected-device extraction, and physical access methods. WiFi users should also shift their mindset — WPA3 is not a guarantee against all password recovery, just against offline handshake cracking.

WPA3 security assessment checklist

  1. 1

    Check your router's security mode

    Log into router admin panel. Look for Wireless Security settings. If it shows WPA3-Personal (SAE) only, the passive-capture offline attack is removed; client downgrade behaviour is then the remaining risk.

  2. 2

    Check for Transition Mode

    If the router shows 'WPA3/WPA2 Mixed' or 'WPA3 Transition', a WPA2 client path exists — crackable via handshake capture on a network you own or are authorized to test.

  3. 3

    Use WPA3-only mode if possible

    If all your devices support WPA3, enable WPA3-only mode in the router settings and enable Transition Disable on clients. This removes the WPA2 fallback.

  4. 4

    For password recovery: use admin panel

    WPA3-only networks require router admin access or connected-device extraction for password recovery.

  5. 5

    Check our WPA3 deep dive

    For the full technical explanation of SAE, Dragonfly, and Dragonblood, read our complete WPA3 vs WPA2 security deep dive.

Frequently Asked Questions

Can WPA3 be cracked?
A passive capture of a WPA3-SAE exchange cannot be attacked offline: the PMK depends on ephemeral secrets the eavesdropper never sees, so there is no check value to test candidates against. Two caveats. WPA3 Transition Mode carries a WPA2 path for WPA2 clients, and that captured handshake is crackable with hashcat mode 22000. And public tools such as wacker can test passwords against a WPA3-SAE access point online at tens of attempts per second — slow, detectable, and dependent on a weak passphrase. Capturing a handshake and recovering its password is lawful only on a network you own or have documented written permission to test.
Why is WPA3 more secure than WPA2?
WPA2's 4-way handshake transmits enough information for an attacker to verify password guesses offline. SAE is a password-authenticated key exchange: the password is never sent, and a passive capture gives an attacker no value to verify a guess against — so the offline attack has no target rather than merely running slowly.
Can I use hashcat to crack WPA3?
No. Hashcat has no mode for SAE and a passive SAE capture cannot be attacked offline, which is not the same as saying no tool can touch it: public tools such as wacker can test passwords against a WPA3-SAE access point online at tens of attempts per second — detectable, and dependent on a weak passphrase. Only WPA2 handshakes captured from WPA3 Transition Mode are crackable with hashcat, and only on a network you own or have documented written permission to test.
What tools work for WPA3?
For capturing WPA3 traffic: hcxdumptool and Wireshark — hcxdumptool detects SAE authentication but does not export it as a crackable artifact, because no hashcat mode exists for it. For auditing your own network: review the SAE group policy and the transition-mode configuration. For password recovery on a WPA3-only network you own: router admin access or connected-device extraction.
Should I upgrade from WPA2 to WPA3?
Yes, if your router and all devices support it. WPA3 adds mandatory PMF and forward secrecy; the stronger 192-bit CNSA cipher suite applies to WPA3-Enterprise rather than WPA3-Personal, which uses the same CCMP-128 as WPA2. WPA3 removes the offline attack on a passive capture. If devices don't support WPA3, transition mode is the bridge — with the caveat that it keeps a WPA2 path open.
Is WPA3 vulnerable to KRACK attacks?
SAE's own exchange is not affected by key reinstallation, but WPA3 still runs the 4-way handshake to install the keys — SAE replaces how the PMK is obtained, not the handshake itself — so WPA3's KRACK resistance rests on the same key-installation countermeasures as patched WPA2, plus PMF, which WPA3 requires and which blocks the forged management frames used to force reconnections.

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