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

CVE-2025-30469: Apple iOS and iPadOS · A person with physical access to an iOS device may be able to access photos from the lock screen in

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 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

2.4Low

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% 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-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

Affected software

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

AI-suggested

To mitigate CVE-2025-30469, organizations and users should promptly update all affected Apple devices to iOS and iPadOS version 18.4 or later, where the vulnerability is fixed. Beyond patching, enforcing strict physical security controls is essential to prevent unauthorized physical access to devices, including policies for device handling, secure storage, and use of device locks such as biometric authentication and strong passcodes. Disabling lock screen access to photos or limiting lock screen widgets and shortcuts can reduce exposure. Organizations should implement mobile device management (MDM) solutions to enforce update policies and monitor device compliance. Educating users about the risks of leaving devices unattended and encouraging immediate reporting of lost or stolen devices will further reduce risk. For highly sensitive environments, consider additional encryption or containerization of sensitive photos and data. Regular audits of device security posture and access logs can help detect potential misuse.

Description

This issue was addressed through improved state management. This issue is fixed in iOS 18.4 and iPadOS 18.4. A person with physical access to an iOS device may be able to access photos from the lock screen.

Impact

The primary impact of CVE-2025-30469 is a breach of confidentiality, as unauthorized individuals with physical access to an iOS or iPadOS device can view photos without unlocking the device. This can lead to privacy violations, exposure of sensitive or personal images, and potential secondary risks such as social engineering or blackmail. Since the vulnerability does not allow modification or deletion of data, integrity and availability remain unaffected. The requirement for physical access limits the scope of exploitation to scenarios involving device theft, loss, or temporary unattended access. Organizations with employees using Apple mobile devices may face risks related to data privacy compliance and insider threats. The vulnerability could be exploited in high-security environments where device confidentiality is critical, such as government, healthcare, or corporate sectors. However, the absence of known exploits and the low CVSS score suggest a limited immediate threat. The impact is mitigated significantly by applying the iOS/iPadOS 18.4 update.

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

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Apr 2026, 01:13 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats