VulnerabilityPublished 11 Dec 2024Updated 2 Apr 2026

CVE-2024-44246: Apple Safari · Out-of-bounds Read

Affects Apple SafariSource CVE Database V5

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

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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 11 Dec 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-44246, affected users and organizations should promptly update Safari and their operating systems to versions 18.2 or later on iOS, iPadOS, and macOS Sequoia 15.2 or later, where the issue is fixed. If you cannot patch yet, users should avoid adding websites to the Safari Reading List while Private Relay is enabled, especially for untrusted or sensitive sites. Organizations can enforce update policies via mobile device management (MDM) solutions to ensure timely patch deployment. Additionally, monitoring network traffic for anomalous direct IP leaks from Safari clients may help detect exploitation attempts. Security teams should educate users about the privacy implications of this vulnerability and encourage cautious use of the Reading List feature. Finally, reviewing and auditing privacy configurations and browser settings can help reduce exposure to similar leaks.

Description

The issue was addressed with improved routing of Safari-originated requests. This issue is fixed in Safari 18.2, iOS 18.2 and iPadOS 18.2, iPadOS 17.7.3, macOS Sequoia 15.2. On a device with Private Relay enabled, adding a website to the Safari Reading List may reveal the originating IP address to the website.

Impact

The primary impact of CVE-2024-44246 is the compromise of user privacy through the leakage of the originating IP address despite Private Relay being enabled. This undermines the core privacy feature of Private Relay, potentially allowing websites to track users or infer their approximate geographic location. For organizations, this could lead to exposure of sensitive user or employee browsing habits and locations, especially in privacy-sensitive sectors such as journalism, activism, or corporate research. While the vulnerability does not allow remote code execution or system compromise, the IP address leakage could facilitate targeted tracking, profiling, or correlation attacks. The scope of affected systems includes all Apple devices running vulnerable Safari versions with Private Relay enabled, which could be widespread given Apple's large market share in mobile and desktop platforms. The requirement for user interaction (adding a site to the Reading List) limits automated exploitation but does not eliminate risk, as users may add sites unknowingly. No integrity or availability impacts reduce the risk of system disruption, but confidentiality loss remains significant for privacy-conscious users and organizations.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Apr 2026, 00:02 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats