CVE-2025-24200
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.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The attack needs physical access to the machine, so a WAF is not on its path.
Also consider: patch · per-resource ACL
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-24200 being exploited?
Yes. CVE-2025-24200 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-24200?
CVE-2025-24200 is rated Medium with a CVSS score of 6.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-24200?
Yes. A fix has been recorded for CVE-2025-24200. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-24200 affect?
CVE-2025-24200 affects apple:ipados, apple:iphone_os. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 15.8.4
- affected< 16.7.11
- affected< 18.3.1
- affected< 17.7.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- partial
Assessed by CISA 13 Feb 2025 (SSVC 2.0.3).
timeline
- 10 Feb 2025Published
- 12 Feb 2025Added to CISA KEV (exploited in the wild) · 1 day later
- 13 Feb 2025CISA SSVC assessment: exploitation active · 1 day later
- 5 Mar 2025CISA remediation due date (US federal agencies) · 20 days later
- 2 Apr 2026CVE record last updated · 394 days (about 1 year) later
- 2 Nov 2026Analysed by vulneraibility.com · 214 days (about 7 months) later
- Linksupport.apple.com /en-us/122173
- Linksupport.apple.com /en-us/122174
- Linksupport.apple.com /en-us/122345
- Linksupport.apple.com /en-us/122346
- Linkseclists.org /fulldisclosure/2025/Feb/7
- Linkseclists.org /fulldisclosure/2025/Feb/8
- Linkseclists.org /fulldisclosure/2025/Apr/7
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-24200
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.