CVE-2026-20674VulnerabilityPublished 11 Feb 2026Updated 2 Apr 2026

CVE-2026-20674: Apple iOS and iPadOS · Information Exposure

Affects Apple iOS and iPadOSSource CVE Database V5

Not known to be exploited · CVSS 4.6 Medium : upgrade to 26.3 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.6Medium

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

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

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 11 Feb 2026
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

Upgrade Apple iOS and iPadOS to 26.3.

Affected software

Product	Affected	Fixed in
AppleiOS and iPadOS	Affected <26.3	Fixed in 26.3

AI-suggested

To mitigate CVE-2026-20674, organizations and users should promptly update all affected Apple devices to iOS and iPadOS version 26.3 or later, where the vulnerability has been fixed. Beyond patching, enforcing strong physical security controls is critical, such as restricting device access, using secure storage, and employing device tracking and remote wipe capabilities. Organizations should implement strict mobile device management (MDM) policies that enforce encryption, lock screen timeouts, and strong passcodes to reduce the risk of unauthorized physical access. Additionally, educating users about the risks of leaving devices unattended and encouraging immediate reporting of lost or stolen devices can limit exposure. For highly sensitive environments, consider disabling features that may expose data on the lock screen or using hardware security modules where available. Regular audits of device security posture and incident response plans for lost or compromised devices will further reduce impact.

Description

A privacy issue was addressed by removing sensitive data. This issue is fixed in iOS 26.3 and iPadOS 26.3. An attacker with physical access to a locked device may be able to view sensitive user information.

Impact

The primary impact of CVE-2026-20674 is the unauthorized disclosure of sensitive user information on locked Apple iOS and iPadOS devices. This can lead to privacy violations, identity theft, or further targeted attacks if the exposed data includes credentials, personal identifiers, or confidential communications. Organizations relying on Apple mobile devices for sensitive communications or data storage could face data breaches or compliance violations if devices are lost or stolen and this vulnerability is exploited. The vulnerability does not affect device integrity or availability, so it does not enable device control or denial of service. However, the ease of physical access exploitation without authentication increases risk in environments where devices may be lost, stolen, or temporarily unattended. This threat is particularly relevant for high-profile individuals, enterprises with mobile workforces, and sectors handling sensitive personal or corporate data. The absence of known exploits in the wild reduces immediate risk but does not eliminate the potential for future attacks.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
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
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.apple.com/en-us/126346 (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:59 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats