CVE-2025-43309VulnerabilityPublished 4 Nov 2025Updated 2 Apr 2026

CVE-2025-43309: Apple iOS and iPadOS · An attacker with physical access to an iOS device may be able to view notification contents from the

Affects Apple iOS and iPadOSSource CVE Database V5

Not known to be exploited · CVSS 2.4 Low.

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.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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 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-43309, organizations and users should promptly update all affected Apple devices to iOS 26 or iPadOS 26, where the vulnerability has been addressed with improved access control checks. Beyond patching, users should configure their devices to minimize notification content visibility on the Lock Screen by adjusting settings to hide sensitive notification previews or disable notifications on the Lock Screen entirely. Enforcing strong physical security controls to prevent unauthorized access to devices is critical, including the use of biometric locks, strong passcodes, and secure storage practices. For enterprise environments, mobile device management (MDM) solutions can enforce notification privacy settings and ensure devices are updated promptly. Educating users about the risks of leaving devices unattended and the importance of applying OS updates can further reduce exposure. Monitoring for lost or stolen devices and enabling remote wipe capabilities can help mitigate risks if physical access is compromised.

Description

A logic issue was addressed with improved checks. This issue is fixed in iOS 26 and iPadOS 26. An attacker with physical access to an iOS device may be able to view notification contents from the Lock Screen.

Impact

The primary impact of CVE-2025-43309 is the unauthorized disclosure of sensitive information contained within notifications on iOS and iPadOS devices. This can lead to privacy breaches, exposure of confidential communications, or leakage of sensitive data such as authentication codes, personal messages, or business-related alerts. While the vulnerability does not allow modification of data or disruption of device functionality, the confidentiality compromise can have serious consequences for individuals and organizations relying on these devices for secure communications. Attackers with physical access could exploit this to gather intelligence or perform social engineering attacks. The impact is limited to devices running affected versions prior to iOS 26 and iPadOS 26, and the requirement for physical access reduces the overall risk. However, in high-risk environments such as government, corporate, or high-profile personal use, the exposure of notification content could facilitate further attacks or privacy violations.

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

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

WeaknessesCWE-284

Technical details

References

Community reviews

Related threats