Physical Activation Lock bypass via path handling
Published Mar 25, 2026 · Updated Mar 25, 2026
Improper access control in Apple iOS and iPadOS before 18.7.7 and 26.0 through 26.1 allows physically proximate attackers to bypass Activation Lock. The iTunes Store component mishandles a path, but Apple has not disclosed the path source, validation error, or operation performed with it. Physical possession of a supported iPhone or iPad is required, and successful exploitation removes the device's ownership-enforcement barrier.
Summary
What happened
Improper access control in Apple iOS and iPadOS before 18.7.7 and 26.0 through 26.1 allows physically proximate attackers to bypass Activation Lock. The iTunes Store component mishandles a path, but Apple has not disclosed the path source, validation error, or operation performed with it. Physical possession of a supported iPhone or iPad is required, and successful exploitation removes the device's ownership-enforcement barrier.
The record
- CVE
- CVE-2025-43534
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-284
- Attack vector
- physical
- 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 <18.7.7
- Affected versionversion=0 <26.2
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