dbcve.org
SafariWeb browser · Apple

CVE-2025-24158

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-27
Fix available
A fix is available. Upgrade to 2.3 / 11.3 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The issue was addressed with improved memory handling. This issue is fixed in Safari 18.3, iOS 18.3 and iPadOS 18.3, macOS Sequoia 15.3, tvOS 18.3, visionOS 2.3, watchOS 11.3. Processing web content may lead to a denial-of-service.

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 · high confidence

Memory handling vulnerability in WebKit that can be triggered by processing malicious web content, leading to denial-of-service. Affects Safari and all Apple operating systems with web browsers. Fixed in Safari 18.3, iOS/iPadOS 18.3, macOS Sequoia 15.3, tvOS 18.3, visionOS 2.3, and watchOS 11.3.

MitigationUpdate all affected Apple devices to the specified versions (Safari 18.3, iOS/iPadOS 18.3, macOS Sequoia 15.3, tvOS 18.3, visionOS 2.3, watchOS 11.3) or later to address the memory handling issue.

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
Affected:< 18.3
IpadosOperating system
Affected:< 18.3
Iphone OsOperating system
Affected:< 18.3
macOSOperating system
Affected:< 15.3
TvosOperating system
Affected:< 18.3
VisionosOperating system
Affected:< 2.3
WatchosOperating system
Affected:< 11.3

CVSS 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
None
Integrity
None
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check macOS version
    Go to Apple menu > About This Mac. The version number is displayed next to macOS name (e.g., 15.2, 15.3, 14.x).
    Affected if The macOS version is below 15.3 (e.g., 15.2, 15.1, 14.x)
  2. Check iOS or iPadOS version
    Open Settings > General > About. The version number is shown next to 'Version' (e.g., 18.2, 18.3).
    Affected if The iOS/iPadOS version is below 18.3 (e.g., 18.2, 18.1, 17.x)
  3. Check Safari version on macOS
    Open Safari > About Safari. The version number appears in the window (e.g., 18.2, 18.3).
    Affected if The Safari version is below 18.3 on macOS
  4. Check tvOS version
    Go to Settings > General > About > Version on Apple TV.
    Affected if The tvOS version is below 18.3
  5. Check visionOS version
    Go to Settings > General > About on Apple Vision Pro.
    Affected if The visionOS version is below 2.3
  6. Check watchOS version
    Open the Watch app on iPhone, go to My Watch > General > About. The version is shown next to 'watchOS'.
    Affected if The watchOS version is below 11.3

If the installed operating system or Safari version is lower than the fixed version (macOS 15.3, iOS/iPadOS 18.3, tvOS 18.3, visionOS 2.3, watchOS 11.3, Safari 18.3), the device is vulnerable to this WebKit memory handling flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.3 / 11.3 / 15.3 or later
Fixed in 2.311.315.3
Interim mitigation

Update all affected Apple devices to the specified versions (Safari 18.3, iOS/iPadOS 18.3, macOS Sequoia 15.3, tvOS 18.3, visionOS 2.3, watchOS 11.3) or later to address the memory handling issue.

Recommended fix High confidence

Safari 18.3, iOS 18.3, iPadOS 18.3, macOS Sequoia 15.3, tvOS 18.3, visionOS 2.3, watchOS 11.3

  1. Check the current version of the affected Apple product (Safari, iOS, iPadOS, macOS, tvOS, visionOS, or watchOS)
  2. For iOS/iPadOS: Go to Settings > General > Software Update and download/install the update
  3. For macOS: Go to System Settings > General > Software Update and download/install the update
  4. For tvOS: Go to Settings > General > Software Update > Download and Install
  5. For watchOS: On iPhone, open Watch app > General > Software Update
  6. For visionOS: Go to Settings > General > Software Update
  7. Safari updates are delivered through the operating system update
  8. After updating, restart/reboot the device to ensure the fix is fully applied
Caveat Standard minor OS update - low risk, but always backup before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24158 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24158 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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