CVE-2025-24193VulnerabilityPublished 31 Mar 2025Updated 2 Apr 2026

CVE-2025-24193: Apple iOS and iPadOS · An attacker with a USB-C connection to an unlocked device may be able to programmatically access

Affects Apple iOS and iPadOSSource CVE Database V5

Not known to be exploited · CVSS 2.4 Low · fixed in 18.4 : update Apple iOS and iPadOS when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

2.4Low

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.4

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

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Mar 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: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

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

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

Affected software

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

AI-suggested

To mitigate CVE-2025-24193, organizations and users should: 1) Immediately update all affected Apple devices to iOS and iPadOS version 18.4 or later, which contains the fix implementing improved authentication for USB-C media access. 2) Enforce strict device locking policies to ensure devices are locked when unattended, minimizing the risk of physical access to unlocked devices. 3) Implement physical security controls to prevent unauthorized physical access to devices, including secure storage and access monitoring. 4) Educate users about the risks of leaving devices unlocked and the importance of using strong passcodes or biometric locks. 5) Consider disabling USB data access when devices are locked if supported by device management policies or configurations. 6) Monitor for any suspicious activity or unauthorized access attempts involving USB connections. These steps go beyond generic advice by emphasizing physical security, user behavior, and device management configurations specific to the vulnerability vector.

Description

This issue was addressed with improved authentication. This issue is fixed in iOS 18.4 and iPadOS 18.4. An attacker with a USB-C connection to an unlocked device may be able to programmatically access photos.

Impact

The primary impact of CVE-2025-24193 is the unauthorized disclosure of photos stored on affected Apple devices. For organizations and individuals, this could lead to privacy violations, exposure of sensitive or confidential images, and potential reputational damage. However, the impact is limited because the attacker must have physical access to an unlocked device, which reduces the likelihood of widespread exploitation. There is no impact on data integrity or device availability, so operational disruption is unlikely. The vulnerability could be exploited in targeted attacks where an adversary gains brief physical access to a device, such as in theft scenarios or insider threats. For enterprises, this risk underscores the importance of physical security controls and device locking policies. Since no known exploits are in the wild, the immediate threat level is low, but unpatched devices remain vulnerable until updated. The vulnerability may also raise concerns for high-profile individuals or organizations handling sensitive media content on Apple devices.

CWE-284Improper Access Control (opens in a new tab)
Pillar weaknessCWE Top 25 (2025): #19OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Embedding Scripts within Scripts (opens in a new tab)
Modification of Windows Service Configuration (opens in a new tab)
Malicious Root Certificate (opens in a new tab)
Intent Spoof (opens in a new tab)
WebView Exposure (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

WeaknessesCWE-284

Technical details

References

Community reviews

Related threats