Passcode-check bypass after Face ID enrollment
Published Jan 9, 2026 · Updated Jan 9, 2026
Authentication bypass in BiometricKit in Apple iOS and iPadOS before 26.2 allows attackers to avoid an immediate passcode check. Apple identifies a validation logic issue but has not disclosed the exact state check that fails during backup restoration. The path requires backup restoration and Face ID enrollment; the reported consequence is a delayed passcode requirement, with no published integrity or availability impact.
Summary
What happened
Authentication bypass in BiometricKit in Apple iOS and iPadOS before 26.2 allows attackers to avoid an immediate passcode check. Apple identifies a validation logic issue but has not disclosed the exact state check that fails during backup restoration. The path requires backup restoration and Face ID enrollment; the reported consequence is a delayed passcode requirement, with no published integrity or availability impact.
The record
- CVE
- CVE-2025-46286
- Published
- Jan 9, 2026
- Updated
- Jan 9, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-288
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 9, 2026CVE publishedPublication date reported by the CVE source.
- Jan 9, 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=unspecified <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