CVE-2026-65359
Apple · iOS, iPadOS, macOS, tvOS, visionOS, watchOS
An out-of-bounds read vulnerability in multiple Apple operating systems allows a local user to cause system termination or read kernel memory.
Executive summary
A critical out-of-bounds read vulnerability in Apple operating systems poses a significant risk to system stability and data confidentiality by allowing local users to access kernel memory.
Vulnerability
This is an out-of-bounds read flaw resulting from insufficient bounds checking, which can be exploited by a local authenticated user to trigger a system crash or disclose sensitive kernel memory.
Business impact
The ability for a local user to read kernel memory constitutes a high-risk security event, as it may expose sensitive data, cryptographic keys, or credentials stored in memory. Furthermore, the potential for unexpected system termination introduces a denial of service risk that could disrupt critical business operations. With a CVSS score of 7.1, this vulnerability is classified as High severity and requires immediate attention to prevent unauthorized information disclosure.
Remediation
Immediate Action: Update all affected Apple devices to the latest versions (iOS/iPadOS 26.7 or 27, macOS 15.8/26.7/27, and tvOS/visionOS/watchOS 27) as specified in the Apple security advisories.
Proactive Monitoring: Monitor system logs for recurring kernel panics or unexplained process terminations that may indicate attempted exploitation of this memory-related flaw.
Compensating Controls: Implement robust endpoint security policies that restrict local user privileges and minimize the number of accounts with access to the underlying operating system environment.
Exploitation status
Public Exploit Available: Unknown
Analyst recommendation
Organizations should prioritize the deployment of these security updates across their mobile and desktop fleets to eliminate the risk of kernel memory exposure. Given the nature of out-of-bounds read vulnerabilities, patching the underlying operating system is the only effective way to remediate the flaw. Security teams should verify that all managed devices have successfully applied the relevant updates to ensure protection against potential local exploitation.
More Apple CVEs all →
History
CVE Brief tracked this CVE 4 days before it had a CVSS score.
- Disclosed CVE record published
- Collected by CVE Brief No CVSS score yet; tracked as early warning
- CVSS score assigned 7.1 (3.1)
- Analyst report written