Private-tab disclosure via faulty state management
Published Mar 8, 2024 · Updated Apr 2, 2026
Authentication bypass in Apple Safari Private Browsing before 17.4 allows attackers to access locked private tabs without authentication. Apple attributes the flaw to Safari Private Browsing state management but has not disclosed the faulty state transition or code locus. User interaction is required, and successful exploitation discloses private-tab content without reported modification or service interruption.
Summary
What happened
Authentication bypass in Apple Safari Private Browsing before 17.4 allows attackers to access locked private tabs without authentication. Apple attributes the flaw to Safari Private Browsing state management but has not disclosed the faulty state transition or code locus. User interaction is required, and successful exploitation discloses private-tab content without reported modification or service interruption.
The record
- CVE
- CVE-2024-23273
- Published
- Mar 8, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-295
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 8, 2024CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <17.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo