CVE-2024-44246
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceWhen Private Relay is enabled in Safari, adding a website to the Reading List can bypass the Private Relay tunnel and expose the user's originating IP address to the target website. The vulnerability stems from improper routing of Safari Reading List requests that should have been anonymized through Private Relay.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 18.2< 17.7.3>= 18.0, < 18.2>= 18.0, < 18.2>= 15.0, < 15.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the Safari versionOpen Safari, go to Safari > About Safari (on Mac) or Settings > Safari > About (on iOS/iPadOS) to view the version numberAffected if The version is below 18.2 for Safari, or the iOS/iPadOS version is below 17.7.3 or below 18.2 but at or above 18.0, or macOS is below 15.2 but at or above 15.0
-
Check if Private Relay is enabledOn Mac: go to Safari > Settings > Privacy and verify the 'Hide IP address from trackers' option is enabled. On iOS/iPadOS: go to Settings > Safari > Privacy & Security and verify 'Hide IP Address' is set to 'From Trackers' or 'From Trackers and Websites'Affected if Private Relay (Hide IP Address) is turned on in Safari settings
-
Verify Reading List functionality usageCheck if the Reading List feature has been used - look for the Reading List icon in Safari's sidebar or toolbar, or check for saved articlesAffected if Any websites have been added to the Reading List while Private Relay was enabled on a vulnerable version
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped15.217.7.318.2
Update affected devices to Safari 18.2, iOS 18.2, iPadOS 18.2, iPadOS 17.7.3, or macOS Sequoia 15.2 to receive the improved routing fix.
Safari 18.2, iOS 18.2, iPadOS 18.2, iPadOS 17.7.3, or macOS Sequoia 15.2 depending on device
- For Safari on macOS: Open the App Store, click Updates, and install the Safari 18.2 update, or go to System Settings > General > Software Update and install macOS Sequoia 15.2
- For iPhone: Go to Settings > General > Software Update and install iOS 18.2
- For iPad: Go to Settings > General > Software Update and install iPadOS 18.2 (or iPadOS 17.7.3 for older devices)
- Alternatively, ensure Automatic Updates are enabled in System Settings/Preferences to receive future security updates automatically
- After updating, verify Private Relay remains enabled in Safari settings if previously configured
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-44246 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-44246 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data