App termination via out-of-bounds access
Published May 11, 2026 · Updated May 11, 2026
Out-of-bounds access in CoreSymbolication in Apple operating systems before 26.5 allows attackers to terminate an app via a crafted file. CoreSymbolication parses attacker-controlled file data without sufficient bounds validation, permitting access outside the intended buffer; Apple has not disclosed whether the operation is a read or write. Exploitation requires user interaction and file parsing, and the documented standalone consequence is app termination.
Summary
What happened
Out-of-bounds access in CoreSymbolication in Apple operating systems before 26.5 allows attackers to terminate an app via a crafted file. CoreSymbolication parses attacker-controlled file data without sufficient bounds validation, permitting access outside the intended buffer; Apple has not disclosed whether the operation is a read or write. Exploitation requires user interaction and file parsing, and the documented standalone consequence is app termination.
The record
- CVE
- CVE-2026-28918
- Published
- May 11, 2026
- Updated
- May 11, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, CWE-125, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
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 <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