dbcve.org
SafariWeb browser · Apple

CVE-2026-39872

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-29
Fix available
A fix is available. Upgrade to 26.5.2 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges 7 weeks old

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 26.5.2, iOS 18.7.10 and iPadOS 18.7.10, iOS 26.5.2 and iPadOS 26.5.2, macOS Tahoe 26.5.2, tvOS 26.6, visionOS 26.6, watchOS 26.6. Processing maliciously crafted web content may lead to an unexpected process crash.

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 confidence

A memory handling vulnerability in WebKit (the browser engine used by Safari and system components) allows remote attackers to cause an unexpected process crash by tricking users into processing maliciously crafted web content. This is a memory corruption issue (likely use-after-free or similar) that can be triggered remotely.

MitigationApply the vendor-supplied updates: Safari 26.5.2, iOS/iPadOS 26.5.2, macOS Tahoe 26.5.2, tvOS 26.6, visionOS 26.6, and watchOS 26.6. Until patched, restrict user access to untrusted websites and enable automatic updates where possible.

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:< 26.5.2
IpadosOperating system
Affected:< 26.5.2
Iphone OsOperating system
Affected:< 26.5.2
macOSOperating system
Affected:< 26.5.2

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 Safari version on macOS
    Open Safari, click Safari menu > About Safari. The version number displayed next to 'Safari' is your installed version.
    Affected if The displayed version number is less than 26.5.2 (for example, 26.5.1, 26.5.0, or earlier)
  2. Check iOS version on iPhone
    Open Settings app > General > About. The 'Version' field shows your installed iOS version.
    Affected if The version number is less than 26.5.2 (for example, 26.5.1, 26.5.0, or earlier)
  3. Check iPadOS version on iPad
    Open Settings app > General > About. The 'Version' field shows your installed iPadOS version.
    Affected if The version number is less than 26.5.2 (for example, 26.5.1, 26.5.0, or earlier)
  4. Verify WebKit-based browser usage
    Identify applications using WebKit rendering engine on your system. Common indicators: Safari itself, or third-party browsers that rely on WebKit. Check application documentation or system profiler for WebKit dependency.
    Affected if Any WebKit-based browser (including Safari) is installed and used on a device running an affected OS version from steps 1-3

You are affected if any Apple device runs Safari, iOS, iPadOS, or macOS Tahoe with a version number lower than 26.5.2 and uses WebKit to process web content.

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 26.5.2 or later
Fixed in 26.5.2
Interim mitigation

Apply the vendor-supplied updates: Safari 26.5.2, iOS/iPadOS 26.5.2, macOS Tahoe 26.5.2, tvOS 26.6, visionOS 26.6, and watchOS 26.6. Until patched, restrict user access to untrusted websites and enable automatic updates where possible.

Recommended fix Moderate confidence

Upgrade to Safari 26.5.2, iOS 26.5.2, iPadOS 26.5.2, or macOS 26.5.2 (macOS Tahoe)

  1. For iOS devices: Go to Settings > General > Software Update and install iOS 26.5.2
  2. For iPadOS devices: Go to Settings > General > Software Update and install iPadOS 26.5.2
  3. For macOS systems: Open System Settings (or System Preferences) > General > Software Update and install macOS 26.5.2
  4. Safari updates are included with the macOS 26.5.2 update; ensure Safari is updated to version 26.5.2

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
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39872 — 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-2026-39872 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