Remote kernel corruption via afpfs buffer overflow
Published Jul 27, 2026 · Updated Jul 27, 2026
Buffer overflow in afpfs in Apple macOS before 14.8.8, 15.7.8, or 26.6 allows remote attackers to crash hosts or corrupt kernel memory. Apple identifies improper bounds checking in afpfs but has not disclosed the affected function, input field, or buffer operation. No authentication or user interaction is required, and successful exploitation interrupts the host or alters kernel memory.
Summary
What happened
Buffer overflow in afpfs in Apple macOS before 14.8.8, 15.7.8, or 26.6 allows remote attackers to crash hosts or corrupt kernel memory. Apple identifies improper bounds checking in afpfs but has not disclosed the affected function, input field, or buffer operation. No authentication or user interaction is required, and successful exploitation interrupts the host or alters kernel memory.
The record
- CVE
- CVE-2026-64767
- Published
- Jul 27, 2026
- Updated
- Jul 27, 2026
- Vendor
- Apple
- Product
- macOS
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 27, 2026CVE publishedPublication date reported by the CVE source.
- Jul 27, 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 <14.8.8
- Affected versionversion=0 <15.7.8
- Affected versionversion=0 <26.6
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