Lock-screen disclosure via insufficient WidgetKit checks
Published May 11, 2026 · Updated May 11, 2026
Improper access control in WidgetKit in Apple iOS and iPadOS before 26.5 allows physically proximate attackers to view restricted lock-screen content. Apple states only that improved checks resolved the WidgetKit privacy issue and has not disclosed the specific check or data path. Exploitation requires physical access to a locked affected iPhone or iPad, and the reported consequence is limited to viewing content the lock screen should withhold.
Summary
What happened
Improper access control in WidgetKit in Apple iOS and iPadOS before 26.5 allows physically proximate attackers to view restricted lock-screen content. Apple states only that improved checks resolved the WidgetKit privacy issue and has not disclosed the specific check or data path. Exploitation requires physical access to a locked affected iPhone or iPad, and the reported consequence is limited to viewing content the lock screen should withhold.
The record
- CVE
- CVE-2026-28965
- Published
- May 11, 2026
- Updated
- May 11, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-284, T1533
- Attack vector
- physical
- 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.
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