VulnerabilityPublished 4 Nov 2025Updated 2 Apr 2026

CVE-2025-43350: Apple iOS and iPadOS · An attacker may be able to view restricted content from the lock screen

Affects Apple iOS and iPadOSSource CVE Database V5

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

Data as of 26 Oct 2026, 14:05 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 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 26.1

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 4 Nov 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 26 Oct 2026.

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 or the CVSS exploit maturity 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-43350, organizations and users should immediately update all affected Apple devices to iOS and iPadOS version 26.1 or later, where the vulnerability is patched. Beyond patching, administrators should review and configure lock screen settings to minimize exposure of sensitive content, such as disabling lock screen notifications for sensitive apps or restricting access to certain features from the lock screen. Employing strong device access controls, including biometric authentication and complex passcodes, can reduce the risk of unauthorized physical access. Organizations should also implement mobile device management (MDM) policies that enforce timely OS updates and restrict lock screen content visibility. Educating users about the risks of leaving sensitive information visible on the lock screen and encouraging prompt reporting of lost or stolen devices will further reduce exposure. Regular audits of device security posture and lock screen configurations can help identify and remediate residual risks. Since no known exploits exist, proactive patching and configuration hardening remain the most effective defenses.

Description

A permissions issue was addressed with additional restrictions. This issue is fixed in iOS 26.1 and iPadOS 26.1. An attacker may be able to view restricted content from the lock screen.

Impact

The primary impact of CVE-2025-43350 is the unauthorized disclosure of restricted content from the lock screen, which can lead to privacy violations for users. While the vulnerability does not compromise device integrity or availability, the exposure of sensitive information such as notifications, messages, or other lock screen content can be exploited for social engineering or targeted attacks. Organizations relying on Apple mobile devices for sensitive communications or data access may face increased risk of information leakage if devices are lost, stolen, or accessed by unauthorized individuals. The low CVSS score reflects the limited scope and difficulty of exploitation, but the impact on confidentiality can be significant in environments where lock screen content contains critical or private information. Since no authentication or user interaction is required, the vulnerability can be exploited quickly if physical access is gained. However, the lack of known exploits in the wild suggests limited active threat currently. Overall, the impact is primarily on user privacy and confidentiality rather than system security or operational continuity.

CWE-276Incorrect Default Permissions (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
During installation, installed file permissions are set to allow anyone to modify those files.
Architecture and Design · Operation
The architecture needs to access and modification attributes for files to only those users who actually require those actions.
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
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
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)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Directory Indexing (opens in a new tab)
Web Server Logs Tampering (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.apple.com/en-us/125632 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Apr 2026, 02:04 UTC

WeaknessesCWE-276

Technical details

References

Community reviews

Related threats