Skip to main content
VulnerabilityPublished Updated

CVE-2023-42939: Apple iOS and iPadOS · A user's private browsing activity may be unexpectedly saved in the App Privacy Report

Affects Apple iOS and iPadOSSource CVE Database V5

0

Not known to be exploited · CVSS 3.3 Low : upgrade to 17.1 when convenient.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score
3.3Low
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 17.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Feb 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

Upgrade Apple iOS and iPadOS to 17.1.

Affected software

ProductAffectedFixed in
Apple iOS and iPadOSAffected
  • <17.1
Fixed in
  • 17.1

AI-suggested

To mitigate CVE-2023-42939, European organizations should: 1) Ensure all Apple iOS and iPadOS devices are updated to version 17.1 or later, where the vulnerability is fixed. 2) Review and restrict access to the App Privacy Report feature, limiting it to trusted users only, to prevent unauthorized viewing of private browsing data. 3) Educate users about the importance of applying updates promptly and maintaining device security to prevent local unauthorized access. 4) Implement mobile device management (MDM) policies that enforce OS updates and control privacy report settings. 5) Regularly audit devices for compliance with privacy policies and monitor for any unusual access to privacy reports. 6) Consider disabling the App Privacy Report feature temporarily if immediate patching is not possible and privacy concerns are critical. These steps go beyond generic advice by focusing on controlling access to the privacy report and leveraging organizational policies to reduce exposure.

Description

A logic issue was addressed with improved checks. This issue is fixed in iOS 17.1 and iPadOS 17.1. A user's private browsing activity may be unexpectedly saved in the App Privacy Report.

References

Community reviews

Loading reviews…