Skip to main content
CVE-2024-23211VulnerabilityPublished Updated

CVE-2024-23211: Apple Safari · A user's private browsing activity may be visible in Settings

Affects Apple SafariSource CVE Database V5

0

Not known to be exploited · CVSS 3.3 Low.

Data as of 26 Oct 2026, 08:11 UTC

CVSS 3.1 base score
3.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Apple SafariAffected
  • =0
Fixed in–

AI-suggested

This vulnerability is addressed by official patches released by Apple. Users and administrators should update affected devices to Safari 17.3 or the corresponding OS versions iOS 16.7.5, iPadOS 16.7.5, iOS 17.3, iPadOS 17.3, or macOS Sonoma 14.3 to remediate this issue. No additional mitigation steps are required beyond applying these updates.

Description

CVE-2024-23211 is a privacy vulnerability in Apple Safari where a user's private browsing activity could be visible in the Settings app. This issue was addressed by Apple through improved handling of user preferences. The vulnerability affects multiple Apple platforms including iOS, iPadOS, and macOS. It has a low severity rating with a CVSS score of 3.3. Apple released fixes for this issue in Safari 17.3, iOS 16.7.5, iPadOS 16.7.

References

Community reviews

Loading reviews…