CVE-2025-24200VulnerabilityPublished 10 Feb 2025Updated 2 Apr 2026

CVE-2025-24200: Apple iOS and iPadOS · A physical attack may disable USB Restricted Mode on a locked device

Affects Apple iOS and iPadOSSource CVE Database V5

Exploited in the wild · KEV due 5 Mar 2025 · 4% EPSS · fixed in 15.8.4 : patch Apple iOS and iPadOS now.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 5 Mar 2025 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS: 4.4% chance of exploitation in 30 days – higher than 91% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 15.8.4

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 10 Feb 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 2 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by apple
2025-01-1700:00Z, 24 days before disclosure
CVE published
on cve.org
2025-02-1019:04Z, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed
2025-02-12, 2 days after disclosure
KEV remediation due
US federal deadline
2025-03-05, 23 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Affected software

Product	Affected	Fixed in
Apple iOS and iPadOS	Affected =0	Fixed in–

Description

An authorization issue was addressed with improved state management. This issue is fixed in iOS 15.8.4 and iPadOS 15.8.4, iOS 16.7.11 and iPadOS 16.7.11, iOS 18.3.1 and iPadOS 18.3.1, iPadOS 17.7.5. A physical attack may disable USB Restricted Mode on a locked device. Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals.

Impact

The primary impact of CVE-2025-24200 is the compromise of confidentiality and integrity of data on affected Apple devices. By disabling USB Restricted Mode, an attacker with physical access can connect USB devices to extract sensitive information or inject malicious payloads without unlocking the device. This can lead to data breaches involving personal, corporate, or government secrets, especially affecting high-value targets such as executives, journalists, activists, or government officials. The vulnerability does not affect device availability but undermines trust in device security controls. Organizations relying on Apple mobile devices for secure communications and data storage face increased risk of espionage, data leakage, and targeted attacks. The exploitation complexity is moderate due to the need for physical access and specialized attack methods, limiting widespread exploitation but posing a critical threat to targeted individuals. The vulnerability may also encourage adversaries to develop advanced forensic or surveillance tools to bypass device protections.

Mitigation

To mitigate CVE-2025-24200, organizations and users should immediately apply the security updates provided by Apple in iOS and iPadOS versions 15.8.4, 16.7.11, 17.7.5, and 18.3.1 or later. Beyond patching, physical security controls must be strengthened to prevent unauthorized access to devices, including secure storage, controlled access environments, and tamper-evident measures. Device management policies should enforce encryption and strong passcodes to reduce the risk of unlocking devices if physical access is gained. Consider disabling USB data connections entirely when devices are locked, if supported by device management solutions. For high-risk users, additional protections such as hardware security modules or secure elements may be warranted. Monitoring for unusual device behavior or unauthorized access attempts can help detect exploitation attempts. Educating users about the risks of physical device compromise and enforcing strict device handling protocols are also critical. Finally, organizations should review and update incident response plans to address potential data breaches stemming from physical attacks on mobile devices.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Apr 2026, 00:47 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats