CVE-2025-24200
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an authorization bypass vulnerability in iOS/iPadOS where a physical attack can disable USB Restricted Mode on a locked device. The issue stems from improper state management in the authorization logic. USB Restricted Mode is designed to block data access via the Lightning port after a device has been locked for a specified period, but this vulnerability allows an attacker with physical access to bypass this protection.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 15.8.4>= 16.0, < 16.7.11>= 17.0, <= 17.7.5>= 18.0, < 18.3.1< 15.8.4>= 16.0, < 16.7.11>= 17.0, < 18.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check iOS version on iPhoneGo to Settings > General > About > Version and note the build numberAffected if Version is less than 15.8.4, or between 16.0 and 16.7.10, or between 17.0 and 17.7.5, or between 18.0 and 18.3.0 (all vulnerable)
-
Check iPadOS version on iPadGo to Settings > General > About > Version and note the build numberAffected if Version is less than 15.8.4, or between 16.0 and 16.7.10, or between 17.0 and 17.7.5, or between 18.0 and 18.3.0 (all vulnerable)
-
Confirm device lock behavior with USB accessoryLock the device, wait over 1 hour, then attempt to connect a USB accessory. If the accessory connects, USB Restricted Mode may have been bypassedAffected if USB accessory successfully connects after device has been locked for more than 1 hour (indicating the bypass may have been exploited)
The device is affected if it runs any iOS version lower than 15.8.4, 16.0-16.7.10, 17.0-17.7.5, or 18.0-18.3.0, as these versions contain the USB Restricted Mode bypass flaw.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped15.8.416.7.1118.3.1
Apply the available iOS/iPadOS security updates (iOS 15.8.4, 16.7.11, 18.3.1; iPadOS 15.8.4, 16.7.17.7.5, 18.3.1) to affected devices. For high-risk individuals targeted by sophisticated attacks, ensure devices are always in secure physical custody and consider additional physical security controls.
iOS 15.8.4 / iPadOS 15.8.4, iOS 16.7.11 / iPadOS 16.7.11, iOS 17.7.5 / iPadOS 17.7.5, or iOS 18.3.1 / iPadOS 18.3.1 depending on your current major version
- 1. Back up your device data before performing the update
- 2. Connect your iPhone or iPad to power and Wi-Fi
- 3. Go to Settings > General > Software Update
- 4. Download and install the appropriate update for your current iOS version: For iOS 15.x devices, install iOS 15.8.4; For iOS 16.x devices, install iOS 16.7.11; For iOS 17.x devices, install iOS 17.7.5; For iOS 18.x devices, install iOS 18.3.1
- 5. After updating, verify the fix by ensuring USB Restricted Mode remains enabled under Settings > Face ID & Passcode (or Touch ID & Passcode) > USB Accessories toggle is disabled when the device is locked
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24200 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24200 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data