System crash via undisclosed Wi-Fi memory handling
Published Feb 11, 2026 · Updated Feb 11, 2026
Memory corruption in Wi-Fi on affected iOS, iPadOS, macOS, and visionOS releases allows local users to crash the system or corrupt kernel memory. Apple identifies the locus only as Wi-Fi and has not disclosed the faulty memory operation or the input that triggers it. Execution of a local app is required; reported outcomes are system termination or kernel-memory corruption, with no disclosed data access or privilege gain.
Summary
What happened
Memory corruption in Wi-Fi on affected iOS, iPadOS, macOS, and visionOS releases allows local users to crash the system or corrupt kernel memory. Apple identifies the locus only as Wi-Fi and has not disclosed the faulty memory operation or the input that triggers it. Execution of a local app is required; reported outcomes are system termination or kernel-memory corruption, with no disclosed data access or privilege gain.
The record
- CVE
- CVE-2026-20621
- Published
- Feb 11, 2026
- Updated
- Feb 11, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-119, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 2026CVE publishedPublication date reported by the CVE source.
- Feb 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <18.7
- Affected versionversion=unspecified <26.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo