Physical disabling of Stolen Device Protection
Published Nov 4, 2025 · Updated Nov 4, 2025
Authentication bypass in Apple iOS and iPadOS before 26.1 allows physically proximate attackers to disable Stolen Device Protection. Apple has not disclosed the decision path or missing validation that permits the protection setting to be disabled. Physical possession of an affected iPhone is required; the reported consequence is loss of the theft-protection control, not data access or code execution.
Summary
What happened
Authentication bypass in Apple iOS and iPadOS before 26.1 allows physically proximate attackers to disable Stolen Device Protection. Apple has not disclosed the decision path or missing validation that permits the protection setting to be disabled. Physical possession of an affected iPhone is required; the reported consequence is loss of the theft-protection control, not data access or code execution.
The record
- CVE
- CVE-2025-43422
- Published
- Nov 4, 2025
- Updated
- Nov 4, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-288
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 4, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record 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=unspecified <26.1
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