CVE-2026-58374: 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
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: hostapd (AlmaLinux:10) 2.11-3.el10_2; hostapd (AlmaLinux:9) 2.11-3.el9_8; hostapd (openSUSE:Leap 16.0) 2.11-bp160.3.1.
Low priority for now. Upgrade to hostapd (AlmaLinux:10) 2.11-3.el10_2; hostapd (AlmaLinux:9) 2.11-3.el9_8; hostapd (openSUSE:Leap 16.0) 2.11-bp160.3.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 30, 2026
- Updated
- Oct 25, 2026
- EPSS
- 0.2% · 22th percentile
- CWE
- CWE-193
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.1
- CNA · mitre
- 6.5
- 0.6 point gap
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| w1.fi | hostapd | cpe:2.3:a:w1.fi:hostapd |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- w1.fi hostapdup to 2.11 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.
w1.fi hostapd
- before 2.12affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | hostapd | before 2.11-3.el10_2 | 2.11-3.el10_2 |
| AlmaLinux:9 | hostapd | before 2.11-3.el9_8 | 2.11-3.el9_8 |
| openSUSE:Leap 16.0 | hostapd | before 2.11-bp160.3.1 | 2.11-bp160.3.1 |
| openSUSE:Leap 16.0 | wpa_supplicant | before 2.11-160000.4.1 | 2.11-160000.4.1 |
| openSUSE:Tumbleweed | hostapd | before 2.11-4.1 | 2.11-4.1 |
| openSUSE:Tumbleweed | wpa_supplicant | before 2.11-7.1 | 2.11-7.1 |
| Red Hat:enterprise_linux:10.2 | hostapd | before 0:2.11-3.el10_2 | 0:2.11-3.el10_2 |
| Red Hat:enterprise_linux:10.2 | hostapd-debuginfo | before 0:2.11-3.el10_2 | 0:2.11-3.el10_2 |
| Red Hat:enterprise_linux:10.2 | hostapd-debugsource | before 0:2.11-3.el10_2 | 0:2.11-3.el10_2 |
| Red Hat:enterprise_linux:9::appstream | hostapd | before 0:2.11-3.el9_8 | 0:2.11-3.el9_8 |
| Red Hat:enterprise_linux:9::appstream | hostapd-debuginfo | before 0:2.11-3.el9_8 | 0:2.11-3.el9_8 |
| Red Hat:enterprise_linux:9::appstream | hostapd-debugsource | before 0:2.11-3.el9_8 | 0:2.11-3.el9_8 |
| Rocky Linux:10 | hostapd | before 0:2.11-3.el10_2 | 0:2.11-3.el10_2 |
| Rocky Linux:9 | hostapd | before 0:2.11-3.el9_8 | 0:2.11-3.el9_8 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | wpa_supplicant | before 2.11-150700.3.3.1 | 2.11-150700.3.3.1 |
| SUSE:Linux Enterprise Server 16.0 | wpa_supplicant | before 2.11-160000.4.1 | 2.11-160000.4.1 |
| SUSE:Linux Micro 6.1 | wpa_supplicant | before 2.11-slfo.1.1_2.1 | 2.11-slfo.1.1_2.1 |
Same product
w1.fi: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-23304The implementations of EAP-pwd in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side-channel attacks as a result of c40Plan
- CVE-2022-23303The implementations of SAE in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side channel attacks as a result of cache40Plan
- CVE-2019-9499The implementations of EAP-PWD in wpa_supplicant EAP Peer do not validate the scalar and element values in EAP-pwd-Commit33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-30004Apr 2, 2021 · In wpa_supplicant and hostapd 2.9, forging attacks may occur because AlgorithmIdentifier parameters are mishandled in tls/pkcs1.c and tls/x521Monitor
- ← EarlierCVE-2022-37660Feb 11, 2025 · In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association.26Monitor
- ← EarlierCVE-2025-24912Mar 12, 2025 · hostapd fails to process crafted RADIUS packets properly.14Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:hostapd | 2.11-3.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| opensuse:hostapd | 2.11-4.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:wpa_supplicant | 2.11-7.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:hostapd | 0:2.11-3.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:hostapd-debuginfo | 0:2.11-3.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:hostapd-debugsource | 0:2.11-3.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| rocky linux:hostapd | 0:2.11-3.el10_2 · Rocky Linux:10 | Package registry (OSV) |
| suse:wpa_supplicant | 2.11-160000.4.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- High
Weakness class (CWE)
CWE-193 · Off-by-one ErrorCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.