VulnerabilityPublished 4 Nov 2025Updated 2 Apr 2026

CVE-2025-43452: Apple iOS and iPadOS · Keyboard suggestions may display sensitive information on the lock screen

Affects Apple iOS and iPadOSSource CVE Database V5

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

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

4.6Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% 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:H/I:N/A:N

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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-43452, organizations and users should promptly update all affected Apple devices to iOS and iPadOS version 26.1 or later, where the vulnerability is fixed by restricting keyboard suggestions on locked screens. Additionally, users should consider disabling keyboard suggestions or predictive text features if immediate updating is not possible, as this reduces the risk of sensitive data exposure. Enforcing strong physical security controls to prevent unauthorized access to devices is critical, including policies for device handling in public or shared spaces. Organizations should implement mobile device management (MDM) solutions to enforce timely updates and configure security settings centrally. Educating users about the risks of exposing sensitive information via predictive text and encouraging cautious typing behavior on mobile devices can further reduce risk. Monitoring for unusual access patterns or physical device tampering complements these technical controls. Finally, reviewing and limiting the types of sensitive information entered on mobile devices, especially when unattended, can minimize potential exposure.

Description

This issue was addressed by restricting options offered on a locked device. This issue is fixed in iOS 26.1 and iPadOS 26.1. Keyboard suggestions may display sensitive information on the lock screen.

Impact

The primary impact of CVE-2025-43452 is the potential unauthorized disclosure of sensitive information through keyboard suggestions displayed on the lock screen. This can lead to confidentiality breaches, especially if sensitive data such as passwords, private messages, or business-critical information is exposed. Attackers with physical access to a locked device could glean confidential information without needing to bypass the lock screen security mechanisms. Although the vulnerability does not affect data integrity or device availability, the exposure of sensitive data can facilitate further attacks such as social engineering, credential theft, or unauthorized access to accounts. Organizations with employees using Apple mobile devices in public or insecure environments are at increased risk. The vulnerability also poses privacy risks to individual users. Since no authentication or user interaction is required, the attack vector is straightforward but limited to physical access scenarios. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers may develop techniques to leverage this vulnerability.

CWE-359Exposure of Private Personal Information to an Unauthorized Actor (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected.
Requirements
Identify and consult all relevant regulations for personal privacy. An organization may be required to comply with certain federal and state regulations, depending on its location, the type of business it conducts, and the nature of any private data it handles.
Architecture and Design
Carefully evaluate how secure design may interfere with privacy, and vice versa. Security and privacy concerns often seem to compete with each other. From a security perspective, all important operations should be recorded so that any anomalous activity can later be identified.
Implementation · Operation · Attack Surface Reduction
Some tools can automatically analyze documents to redact, strip, or "sanitize" private information, although some human review might be necessary. Tools may vary in terms of which document formats can be processed.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V10.2.1 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Evercookie (opens in a new tab)
Cross Site Identification (opens in a new tab)
Probe iOS Screenshots (opens in a new tab)
Shoulder Surfing (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:24 UTC

WeaknessesCWE-359

Technical details

References

Community reviews

Related threats