System termination or kernel-memory write via HFS overflow
Published May 11, 2026 · Updated May 11, 2026
Buffer overflow in HFS in macOS Sonoma before 14.8.7, Sequoia before 15.7.7, and Tahoe before 26.5 allows apps to write kernel memory. The HFS component performs a buffer copy without sufficient bounds checking, allowing input to exceed its destination buffer. A locally running app is required; successful triggering can write kernel memory or crash the operating system, while the affected HFS function and input path remain undisclosed.
Summary
What happened
Buffer overflow in HFS in macOS Sonoma before 14.8.7, Sequoia before 15.7.7, and Tahoe before 26.5 allows apps to write kernel memory. The HFS component performs a buffer copy without sufficient bounds checking, allowing input to exceed its destination buffer. A locally running app is required; successful triggering can write kernel memory or crash the operating system, while the affected HFS function and input path remain undisclosed.
The record
- CVE
- CVE-2026-28925
- Published
- May 11, 2026
- Updated
- May 11, 2026
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-120, T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 11, 2026CVE publishedPublication date reported by the CVE source.
- May 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=0 <14.8.7
- Affected versionversion=0 <15.7.7
- Affected versionversion=0 <26.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
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