CVE-2025-30468: Apple iOS and iPadOS · Private Browsing tabs may be accessed without authentication
Affects Apple iOS and iPadOSSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apple iOS and iPadOS | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-30468, organizations and users should promptly update all affected Apple devices to iOS 26 and iPadOS 26 or later, where the vulnerability is fixed. Enforcing automatic updates or centralized device management policies can ensure timely patch deployment. Additionally, organizations should implement strict access controls on devices, including strong passcodes, biometric authentication, and device encryption to prevent unauthorized physical access. Network-level protections such as VPNs and firewalls can reduce exposure to remote exploitation attempts. Monitoring device logs for unusual browsing activity or unauthorized access attempts can help detect exploitation. Educating users about the risks of using private browsing on untrusted networks and encouraging cautious behavior can further reduce risk. For high-security environments, consider disabling private browsing features temporarily until patches are applied. Finally, coordinate with Apple support and security advisories to stay informed about any emerging exploits or additional mitigations.
Description
This issue was addressed through improved state management. This issue is fixed in iOS 26 and iPadOS 26. Private Browsing tabs may be accessed without authentication.