Kernel-memory write or system termination via bounds error
Published Sep 14, 2026 · Updated Sep 14, 2026
An out-of-bounds write in macOS before 15.8, 26.7, and 27 allows local users to terminate the system or write kernel memory. Apple states that bounds checking was inadequate but has not published the affected component, input path, or precise write operation. Exploitation requires execution of an app on the Mac; the bounded consequences are unexpected system termination or a write to kernel memory.
Summary
What happened
An out-of-bounds write in macOS before 15.8, 26.7, and 27 allows local users to terminate the system or write kernel memory. Apple states that bounds checking was inadequate but has not published the affected component, input path, or precise write operation. Exploitation requires execution of an app on the Mac; the bounded consequences are unexpected system termination or a write to kernel memory.
The record
- CVE
- CVE-2026-84619
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- Apple
- Product
- macOS
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 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=0 <15.8
- Affected versionversion=0 <26.7
- Affected versionversion=0 <27
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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