Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-46286: Restoring from a backup may prevent passcode from being required immediately after Face ID enrollment in Apple iOS and iPadOS

0
Medium
VulnerabilityCVE-2025-46286cvecve-2025-46286
Published: Fri Jan 09 2026 (01/09/2026, 21:14:39 UTC)
Source: CVE Database V5
Vendor/Project: Apple
Product: iOS and iPadOS

Description

A logic issue was addressed with improved validation. This issue is fixed in iOS 26.2 and iPadOS 26.2. Restoring from a backup may prevent passcode from being required immediately after Face ID enrollment.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/03/2026, 02:41:17 UTC

Technical Analysis

CVE-2025-46286 is a logic vulnerability identified in Apple’s iOS and iPadOS operating systems affecting the authentication flow after Face ID enrollment. Specifically, when a user restores their device from a backup, the system may fail to immediately require the passcode that normally follows Face ID setup. This occurs due to inadequate validation checks in the backup restoration process, allowing the device to bypass the passcode prompt temporarily. The vulnerability is classified under CWE-288 (Authentication Bypass Using an Alternate Path or Channel). The flaw does not affect the integrity or availability of the system but impacts confidentiality by potentially allowing unauthorized access to the device’s data before the passcode is enforced. The CVSS v3.1 base score is 4.3 (medium), reflecting network attack vector, low attack complexity, no privileges required, user interaction required, and limited confidentiality impact. Apple addressed this issue in iOS and iPadOS version 26.2 by improving validation logic to ensure the passcode is required immediately after Face ID enrollment, even following a backup restore. No public exploits or active exploitation in the wild have been reported to date. The vulnerability primarily affects all devices running vulnerable versions of iOS and iPadOS prior to 26.2, which includes a broad range of Apple iPhones and iPads globally.

Potential Impact

The primary impact of CVE-2025-46286 is a temporary weakening of device security post-backup restoration, where the passcode requirement is delayed after Face ID enrollment. This can allow an attacker with physical access to the device to bypass the passcode prompt momentarily, potentially gaining unauthorized access to sensitive data stored on the device. While the vulnerability does not affect system integrity or availability, the confidentiality of user data is at risk during this window. Organizations relying on Apple mobile devices for sensitive communications, data storage, or access to corporate resources could face increased risk of data exposure if devices are restored from backups without applying the patch. This is particularly concerning in environments where devices are frequently restored or reset, such as in IT asset management, device recycling, or incident response scenarios. Although exploitation requires physical access and user interaction (restoring a backup), the low complexity and lack of privilege requirements make it a notable risk for insider threats or opportunistic attackers. The absence of known exploits in the wild reduces immediate risk but does not eliminate the potential for future exploitation.

Mitigation Recommendations

To mitigate CVE-2025-46286, organizations and users should promptly update all affected Apple devices to iOS and iPadOS version 26.2 or later, where the vulnerability has been fixed. Device management policies should enforce timely OS updates and restrict restoration of backups to trusted sources only. IT administrators should audit device restoration procedures to ensure compliance with security policies and consider additional controls such as requiring device encryption and strong passcodes. Physical security controls should be enhanced to prevent unauthorized access to devices, especially during restoration or provisioning phases. For environments with high security requirements, consider disabling automatic backup restoration or implementing multi-factor authentication mechanisms where possible. Monitoring and logging of device restoration events can help detect suspicious activities related to this vulnerability. Finally, educating users about the risks of restoring backups from untrusted sources and the importance of applying security updates is critical.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
apple
Date Reserved
2025-04-22T21:13:49.959Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 696175d145ea0302aa963f44

Added to database: 1/9/2026, 9:40:33 PM

Last enriched: 4/3/2026, 2:41:17 AM

Last updated: 5/8/2026, 7:24:32 PM

Views: 237

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses