Contact disclosure via Siri lock-screen bypass
Published Sep 16, 2024 · Updated Apr 2, 2026
Information disclosure in Siri in Apple iOS and iPadOS before 18 allows physically proximate attackers to access contacts from the lock screen. Apple identifies the affected locus as Siri but has not disclosed which lock-screen check failed or how contact access bypassed it. Physical possession of a locked, affected iPhone or iPad is required; the documented consequence is access to stored contact information.
Summary
What happened
Information disclosure in Siri in Apple iOS and iPadOS before 18 allows physically proximate attackers to access contacts from the lock screen. Apple identifies the affected locus as Siri but has not disclosed which lock-screen check failed or how contact access bypassed it. Physical possession of a locked, affected iPhone or iPad is required; the documented consequence is access to stored contact information.
The record
- CVE
- CVE-2024-44139
- Published
- Sep 16, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-200, T1005
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2024CVE publishedPublication date reported by the CVE source.
- Apr 2, 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 <18
What conditions does exploitation require?
What is affected?
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