Kernel code execution via Wi-Fi memory corruption
Published May 26, 2022 · Updated May 30, 2025
Memory corruption in the Wi-Fi component of Apple macOS allows local applications to execute arbitrary code with kernel privileges. Apple has not disclosed the corrupted object, triggering input, or incorrect memory operation beyond stating that Wi-Fi used improper memory handling. A locally running application is required; successful exploitation grants kernel-level code execution and control of the host.
Summary
What happened
Memory corruption in the Wi-Fi component of Apple macOS allows local applications to execute arbitrary code with kernel privileges. Apple has not disclosed the corrupted object, triggering input, or incorrect memory operation beyond stating that Wi-Fi used improper memory handling. A locally running application is required; successful exploitation grants kernel-level code execution and control of the host.
The record
- CVE
- CVE-2022-26761
- Published
- May 26, 2022
- Updated
- May 30, 2025
- Vendor
- Apple
- Product
- Security Update Catalina
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2022CVE publishedPublication date reported by the CVE source.
- May 30, 2025Record 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 <2022
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.
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