Security Advisory

CVE-2019-9494: Dragonblood SAE Side Channel (WPA3)

Last updated:
  • CVE-2019-9494

CVE-2019-9494 is the Dragonblood side-channel flaw in the WPA3-Personal (SAE) code of hostapd and wpa_supplicant up to 2.7: timing differences and cache access patterns leak information about the Wi-Fi password, enough for an offline dictionary attack. It affects SAE-enabled routers and clients, including Synology RT2600ac and MR2200ac on SRM 1.2.

Vulnerability summary

CVSS base score

5.9

Medium severity

EPSS score (FIRST)

3.9%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2019-9494 · Source: NVD

Affected components

ComponentCPEVersion range
hostapd and wpa_supplicant (w1.fi hostap project) with SAE supportcpe:2.3:a:w1.fi:hostapd:*:*:*:*:*:*:*:*up to and including 2.7 with CONFIG_SAE=y and SAE enabled at runtime; fixed in 2.8 (w1.fi 2019-1)
Synology Router Manager (SRM) 1.2 on RT2600ac and MR2200ac routerscpe:2.3:a:synology:router_manager:*:*:*:*:*:*:*:*SRM 1.2 before 1.2.3-8017 (Synology-SA-19:16)

What does this mean for affected devices?

CVE-2019-9494 is one of the Dragonblood findings by Mathy Vanhoef and Eyal Ronen against SAE (Simultaneous Authentication of Equals), the handshake behind WPA3-Personal. NVD's record says the SAE implementations in hostapd and wpa_supplicant "are vulnerable to side channel attacks as a result of observable timing differences and cache access patterns" and that "both hostapd with SAE support and wpa_supplicant with SAE support prior to and including version 2.7 are affected". NVD scores it 5.9 under CVSS v3.1, vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, with CWE-203 (observable discrepancy) as primary weakness (NVD).

The w1.fi 2019-1 advisory, published 2019-04-10, separates two attacks. The cache attack targets SAE with ECC groups, including mandatory group 19, and needs the attacker "to be able to run unprivileged code on the victim machine". Upstream notes this "is not commonly the case on access points, so the most likely target for this would be a client device". The timing attack applies only to MODP groups 22, 23 and 24, which must be enabled explicitly in sae_groups and are off by default. The vulnerable configuration is any build with CONFIG_SAE=y and SAE enabled at runtime. The fix is a set of constant-time patches, shipped in hostapd and wpa_supplicant 2.8; w1.fi later issued follow-ups in its 2019-6 and 2022-1 advisories.

The device angle is consumer and small-office routers that offered WPA3 early. Synology-SA-19:16, published 2019-04-11, lists Synology Router Manager (SRM) 1.2 on the RT2600ac and MR2200ac as affected by Dragonblood and CVE-2019-9494 at moderate severity, with SRM 1.2.3-8017 or later as the fix and a patch for SRM 1.2.1 and later. Synology scores CVE-2019-9494 at 5.3 with an adjacent-network vector. The same advisory lists RADIUS Server 3.0 as affected by the related EAP-pwd CVEs.

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.03878, the 90.38th percentile, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS). On a locked-down access point that runs no third-party code, the cache attack is hard to mount; on clients that run apps, such as phones, it matters more.

To fix it, ship hostapd and wpa_supplicant 2.8 or later, or backport the 2019-1 patches, keep MODP groups out of sae_groups, and require strong passphrases so an offline dictionary attack fails. Our hostapd and wpa_supplicant vulnerabilities guide shows how to find CONFIG_SAE and the version in an image, and our weak cryptography fix guide covers constant-time code in firmware. For the earlier WPA2 key reinstallation flaws in the same code base, see CVE-2017-13077.

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • SAE in hostapd and wpa_supplicant leaks via timing and cache patterns; versions up to and including 2.7 with SAE; NVD CVSS v3.1 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N), CWE-203. — NVD
  • Cache attack needs unprivileged code on the victim, most likely a client; timing attack only for MODP groups 22-24, disabled by default; CONFIG_SAE=y plus runtime SAE; fixed in v2.8. — w1.fi security advisory 2019-1
  • Synology-SA-19:16: SRM 1.2 (RT2600ac, MR2200ac) affected, moderate, fixed in SRM 1.2.3-8017; Synology CVSS 5.3. — Synology-SA-19:16
  • Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.03878 (90.38th percentile), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. w1.fi security advisory 2019-1: SAE side-channel attacks
  3. Synology-SA-19:16: Dragonblood
  4. CISA KEV
  5. FIRST EPSS

Frequently asked questions

Does CVE-2019-9494 affect a router that does not offer WPA3?

No. The w1.fi 2019-1 advisory lists the vulnerable configuration as hostapd or wpa_supplicant built with CONFIG_SAE=y and with SAE enabled in the runtime configuration. A WPA2-only build or configuration does not use the affected code.

Is a WPA3 access point or a WPA3 client more at risk?

The client. The cache attack needs the attacker to run unprivileged code on the victim device, which w1.fi says is not commonly the case on access points, so the most likely target is a client device. The timing attack needs MODP groups 22 to 24, which are disabled by default.

Which Synology routers were affected and how were they fixed?

Synology-SA-19:16 lists SRM 1.2 on the RT2600ac and MR2200ac and names SRM 1.2.3-8017 or later as the fix, with a patch for SRM 1.2.1 and later (per Synology).

Is CVE-2019-9494 in the CISA KEV catalog?

No, not as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.03878, the 90.38th percentile, in the 2026-11-15 dataset (per CISA KEV and FIRST EPSS).