VulnerabilityPublished 28 Oct 2024Updated 2 Apr 2026

CVE-2024-44229: Apple Safari · Private browsing may leak some browsing history

Affects Apple SafariSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 18.1 : update Apple Safari when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.1

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: None: The vulnerable system can be exploited without any interaction from any user.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 28 Oct 2024
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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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

Affected software

Product	Affected	Fixed in
Apple Safari	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2024-44229, organizations and users should: 1) Immediately update Safari to version 18.1 or later and ensure that iOS, iPadOS, macOS Sequoia, and visionOS are updated to their respective patched versions (iOS/iPadOS 18.1, macOS 15.1, visionOS 2.1). 2) Enforce policies that mandate timely application of security updates on all Apple devices within the organization. 3) Educate users about the limitations of private browsing and encourage cautious behavior when handling sensitive information, even in private mode. 4) Monitor for unusual network activity that could indicate attempts to exploit information leakage vulnerabilities. 5) Consider additional privacy tools or browser extensions that enhance private browsing protections if organizational risk tolerance is low. 6) Review and audit internal privacy policies to ensure they account for potential browser-based information leaks. These steps go beyond generic patching advice by emphasizing user education, monitoring, and policy enforcement tailored to privacy protection.

Description

An information leakage was addressed with additional validation. This issue is fixed in Safari 18.1, iOS 18.1 and iPadOS 18.1, macOS Sequoia 15.1, visionOS 2.1. Private browsing may leak some browsing history.

Impact

The primary impact of CVE-2024-44229 is the compromise of user privacy through leakage of browsing history in Safari’s private browsing mode. This undermines the fundamental expectation that private browsing sessions do not retain or expose browsing data. For individuals, this could lead to exposure of sensitive or confidential browsing activities. For organizations, especially those with employees or clients using Safari on Apple devices, this could result in inadvertent disclosure of sensitive research, competitor analysis, or confidential information. While the vulnerability does not affect system integrity or availability, the confidentiality breach could facilitate targeted phishing, social engineering, or surveillance attacks. Given the widespread use of Apple devices globally, the scope of affected users is large. However, the lack of known exploits and the medium severity rating suggest the risk is moderate but should not be ignored, particularly in privacy-sensitive environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Apr 2026, 23:59 UTC

Technical details

References

Community reviews

Related threats