VulnerabilityPublished 25 Mar 2026Updated 26 Oct 2026

CVE-2026-20668: Apple iOS and iPadOS · Sensitive Data in Logs

Affects Apple iOS and iPadOSSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.5 Medium : upgrade to 26.3 or 18.7.7 when convenient.

Data as of 30 Oct 2026, 12:04 UTC

CVSS 3.1 base score

5.5Medium

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

Thin evidence

One scorer or none

CVSS scores by source
CISA-ADP	CVSS 3.1	5.5

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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 25 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Upgrade iOS and iPadOS to 26.3 or 18.7.7; macOS to 26.3, 15.7.5 or 14.8.5; visionOS to 26.3.

Affected software

Product	Affected	Fixed in
AppleiOS and iPadOS	Affected <26.3	Fixed in 26.3
AppleiOS and iPadOS	Affected <18.7.7	Fixed in 18.7.7
ApplemacOS	Affected <26.3	Fixed in 26.3
ApplemacOS	Affected <15.7.5	Fixed in 15.7.5
ApplemacOS	Affected <14.8.5	Fixed in 14.8.5
ApplevisionOS	Affected <26.3	Fixed in 26.3

AI-suggested

To mitigate CVE-2026-20668, organizations and users should immediately apply the security updates released by Apple for iOS 18.7.7, iPadOS 18.7.7, macOS Sequoia 15.7.5, macOS Sonoma 14.8.5, macOS Tahoe 26.3, and visionOS 26.3. Beyond patching, organizations should audit app permissions and restrict installation of untrusted or unnecessary applications to reduce the risk of malicious apps exploiting this vulnerability. Implement mobile device management (MDM) solutions to enforce security policies and monitor device logs for suspicious activity. Educate users about the risks of installing unknown apps and the importance of prompt system updates. Additionally, review logging configurations to ensure sensitive data is not unnecessarily logged and consider encrypting logs or restricting access to log files. Regularly monitor threat intelligence sources for any emerging exploit attempts related to this vulnerability.

Description

A logging issue was addressed with improved data redaction. This issue is fixed in iOS 18.7.7 and iPadOS 18.7.7, iOS 26.3 and iPadOS 26.3, macOS Sequoia 15.7.5, macOS Sonoma 14.8.5, macOS Tahoe 26.3, visionOS 26.3. An app may be able to access sensitive user data.

Impact

The primary impact of CVE-2026-20668 is the potential unauthorized disclosure of sensitive user data on affected Apple devices. This could include personal information, credentials, or other confidential data inadvertently captured in logs. While the vulnerability does not affect data integrity or system availability, the confidentiality breach could lead to privacy violations, identity theft, or further targeted attacks if sensitive information is exposed. Organizations relying heavily on Apple mobile devices and macOS systems for business operations, especially those handling sensitive or regulated data, face increased risk of data leakage. The requirement for local access and user interaction limits remote exploitation but does not eliminate risk from malicious apps or insiders. The absence of known exploits reduces immediate threat but does not preclude future attacks. Overall, the vulnerability could undermine user trust and compliance with data protection regulations if not addressed promptly.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (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, 02:58 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats