System termination or kernel corruption via Telephony overflow
Published Mar 25, 2026 · Updated Mar 25, 2026
Buffer overflow in Telephony in Apple iOS and iPadOS before 26.4 allows remote attackers to crash devices or corrupt kernel memory. Apple identifies inadequate bounds checking in Telephony but has not published the parser, message type, or buffer operation that mishandles remote input. Reachability requires remote access to the affected telephony path; successful exploitation terminates the system or corrupts kernel memory.
Summary
What happened
Buffer overflow in Telephony in Apple iOS and iPadOS before 26.4 allows remote attackers to crash devices or corrupt kernel memory. Apple identifies inadequate bounds checking in Telephony but has not published the parser, message type, or buffer operation that mishandles remote input. Reachability requires remote access to the affected telephony path; successful exploitation terminates the system or corrupts kernel memory.
The record
- CVE
- CVE-2026-28858
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 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.4
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