SafariWeb browser · Apple
CVE-2025-24143
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 access restrictions to the file system. This issue is fixed in Safari 18.3, iOS 18.3 and iPadOS 18.3, macOS Sequoia 15.3, visionOS 2.3. A maliciously crafted webpage may be able to fingerprint the user.
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 confidenceA file system access vulnerability in WebKit allows malicious webpages to enumerate file system properties or metadata, enabling user fingerprinting. The fix implements improved access restrictions to prevent unauthorized file system information leakage through the browser.
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
SafariWeb browser
< 18.3< 18.3< 15.3< 2.3CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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.
-
Identify the browser being usedCheck if Safari is the default or active browser. On Apple platforms, also note if a WebKit-based browser (like Safari, WebKit-nightly, or browsers using WebKit) is in use.Affected if Safari or any WebKit-based browser is active on the system
-
Check Safari version on macOSOpen Safari, go to Safari menu > About Safari. Compare the version number to 18.3.Affected if Safari version is below 18.3 (e.g., 18.2.x or earlier)
-
Check macOS versionOpen System Settings > About. Compare the macOS version to 15.3.Affected if macOS version is below 15.3 (e.g., 15.2, 14.x, 13.x)
-
Check iOS/iPadOS versionGo to Settings > General > About on iPhone or iPad. Compare the iOS version to 18.3.Affected if iOS or iPadOS version is below 18.3
-
Check visionOS versionGo to Settings > About on Apple Vision. Compare the version to 2.3.Affected if visionOS version is below 2.3
The environment is affected if Safari (or any WebKit-based browser on Apple platforms) is running on macOS < 15.3, iOS/iPadOS < 18.3, or visionOS < 2.3, or if Safari version is < 18.3 regardless of OS 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 · scoped2.315.318.3
Update affected devices to Safari 18.3, iOS/iPadOS 18.3, macOS Sequoia 15.3, or visionOS 2.3 to obtain the patched WebKit components.
Safari 18.3, iOS 18.3, iPadOS 18.3, macOS Sequoia 15.3, visionOS 2.3
- For macOS: Open System Settings > General > Software Update and upgrade to macOS Sequoia 15.3
- For iOS: Go to Settings > General > Software Update and upgrade to iOS 18.3
- For iPadOS: Go to Settings > General > Software Update and upgrade to iPadOS 18.3
- For visionOS: Go to Settings > General > Software Update and upgrade to visionOS 2.3
- For Safari: The browser updates automatically with macOS/iOS updates; ensure the OS is updated to the versions above
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Safari
Scoped from the published advisory
- 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-2025-24143 — 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-2025-24143 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