In hostapd before 2.12, a missing bounds check in AP-mode Wi-Fi 7 (IEEE 802.11be) Multi-Link Operation (MLO) association request processing allows an unauthenticated attacker within wireless range to send a crafted management frame containing a malformed Multi-Link Element or Per-STA Profile subelement. In hostapd_process_ml_assoc_req() in src/ap/ieee802_11_eht.c, the received link_id field can be parsed as value 15, but the corresponding links[] storage only has valid entries for lower link IDs (0 through 14). This causes an out-of-bounds write / small memory corruption during association processing before the 4-way handshake. The attack does not require network credentials, prior authentication, or user interaction. The confirmed practical impact is denial of service through hostapd process termination. This affects hostapd v2.11 and newer development snapshots before v2.12 when built with CONFIG_IEEE80211BE enabled. The issue is fixed in hostapd v2.12 and the upstream 2026-1 fixes.
CVE-2026-58374
Score 6.5 from GitHub Security Advisory published 2026-06-30. NVD baseline CVSS 7.1; sources differ by 0.6.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 6.5(high)
- EPSS
- 20.1%
- KEV
- Not listed
Published
June 30, 2026
Last Modified
July 2, 2026
Advisory Details (5)
Auto-updated Jun 30, 2026oss-security - hostapd: OOB write in Wi-Fi 7 MLD association parsing (pre-auth DoS)
https://www.openwall.com/lists/oss-security/2026/06/30/1BSS: Add bounds check for link_id in Basic MLE parsing - hostap - hostapd/wpa_supplicant
https://git.w1.fi/cgit/hostap/commit/?id=aa9d345887389a251c63a3781d2ad2940d079193AP MLD: Fix link ID validation in Basic MLE parsing - hostap - hostapd/wpa_supplicant
https://git.w1.fi/cgit/hostap/commit/?id=46dd5a4ffc9bcf44cf8fc45120b3e1e5ec922187Vendor Advisories for CVE-2026-58374(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 24× in last 7d / 24× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 15:22 UTCEG score recompute
- 2026-07-06 15:21 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 15:13 UTCEG score recompute
- 2026-07-05 15:13 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 15:05 UTCEG score recompute
- 2026-07-04 15:05 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 14:58 UTCEG score recompute
- 2026-07-03 14:57 UTCGHSA enrichment
- 2026-07-03 04:38 UTCNVD updateCVSS v3 → 7.1 · severity → HIGH
- 2026-07-02 14:47 UTCEG score recompute
- 2026-07-02 14:47 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 14:40 UTCEG score recompute
- 2026-07-01 14:40 UTCGHSA enrichment
- 2026-06-30 14:33 UTCEG score recompute
- 2026-06-30 14:32 UTCNVD updatefirst tracked
Frequently asked(5)
What is CVE-2026-58374?
When was CVE-2026-58374 disclosed?
Is CVE-2026-58374 actively exploited?
What is the CVSS score of CVE-2026-58374?
How do I remediate CVE-2026-58374?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58374
Is Your Infrastructure Affected by CVE-2026-58374?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.