Apple iOS and iPadOS Incorrect Authorization Vulnerability (CVE-2025-24200)

Apple iOS and iPadOS contains an incorrect authorization vulnerability that allows a physical attacker to disable USB Restricted Mode on a locked device.

Published Feb 10, 2025 · Updated May 29, 2026

X LinkedIn

Why patchRisk explained in plain English

Worst-case scenarioIf unpatched

An attacker, without authentication, can achieve full data confidentiality loss, arbitrary modification of data. Federal agencies are required to remediate by 2025-03-05 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Incorrect Authorization (CWE-863) vulnerability in Apple iOS and iPadOS. 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. Exploitation requires physical access, low attack complexity, no authentication required, and no user interaction required.

Am I affected?Quick check

Probably yes if any of these apply:

●Apple Device Administrators

●Endpoint Security

●IT Security

●Running ipados: v < 15.8.4, 16.0 ≤ v < 16.7.11, 17.0 ≤ v ≤ 17.7.5, 18.0 ≤ v < 18.3.1; iphone os: v < 15.8.4, 16.0 ≤ v < 16.7.11, 17.0 ≤ v < 18.3.1

Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2025-02-12 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2025-03-05.

How to patch

Get the fix

Apply the fixed package from your vendor. The advisory lists affected versions and the exact fixed build.

↗ Vendor advisory

Manual remediation steps

Identify affected hosts: query inventory for general installs in scope.

Apply the vendor security update referenced in CVE-2025-24200's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.

Verify the fix per the vendor's published verification steps.

Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.

PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References