CVE-2025-24912
W1.Fi Hostapd ≤ 2.11
Raw vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LSummary
CVE-2025-24912 is a low-severity Premature Release of Resource During Expected Lifetime (CWE-826) vulnerability in W1.Fi Hostapd. Its CVSS base score is 3.7 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-7660
Vulnerability Data
hostapd fails to process crafted RADIUS packets properly. When hostapd authenticates wi-fi devices with RADIUS authentication, an attacker in the position between the hostapd and the RADIUS server may inject crafted RADIUS packets and force RADIUS authentications to fail.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover premature-release defects before deployment.
Engineering principles can require correct resource lifetime management so the premature-release pattern is never coded.
Process isolation confines the blast radius when a resource is released while still referenced inside another domain.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect premature-release bugs, providing partial mitigation.
Secure development lifecycle practices can include resource-lifetime checks that reduce premature-release defects.
Application security requirements can mandate explicit resource-release rules, partially addressing the weakness.
Secure architecture principles encourage proper resource scoping and lifetime management.
Secure coding standards directly prohibit premature resource release, covering most of the weakness.
Change-management processes may catch resource-handling regressions but do not directly prevent the weakness.