dbcve.org
SafariWeb browser · Apple

CVE-2026-43746

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
A use-after-free issue was addressed with improved memory management. This issue is fixed in Safari 26.5.2, iOS 26.5.2 and iPadOS 26.5.2, macOS Tahoe 26.5.2. Processing maliciously crafted web content may lead to an unexpected Safari 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 use-after-free vulnerability in Safari's web content processing allows remote attackers to cause a crash by tricking users into visiting malicious websites. The vulnerability stems from improper memory management when handling crafted web content.

MitigationUpdate affected systems to Safari 26.5.2, iOS 26.5.2, iPadOS 26.5.2, or macOS Tahoe 26.5.2. Until patched, restrict web browsing to trusted sites and disable JavaScript if 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.0, < 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. Identify the Apple product running Safari
    Determine if the system is running Safari on macOS, iOS, iPadOS, or another Apple platform. On macOS, check System Settings > General > About. On iOS/iPadOS, go to Settings > General > About.
    Affected if Any Apple product running Safari is potentially affected
  2. Locate the Safari browser version
    In Safari, click Safari > About Safari to see the version number. On iOS/iPadOS, the Safari version matches the iOS/iPadOS version shown in Settings > General > About.
    Affected if The Safari version displayed is below 26.5.2
  3. Confirm macOS version if applicable
    If running Safari on macOS, run 'sw_vers' in Terminal or check System Settings > General > About. Note that macOS versions 26.0 through 26.5.2 are specifically in scope.
    Affected if macOS version is 26.0, 26.1, 26.2, 26.3, 26.4, or 26.5.1 (any version >= 26.0 but < 26.5.2)
  4. Verify web content processing is accessible
    The vulnerability triggers through crafted web content. Confirm Safari is used for web browsing and JavaScript handling is enabled in Safari preferences.
    Affected if Safari is actively used for web browsing with standard settings enabled

A user is affected if their Safari version is below 26.5.2 (or for macOS specifically, between 26.0 and 26.5.1) and they use the browser for 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

Update affected systems to Safari 26.5.2, iOS 26.5.2, iPadOS 26.5.2, or macOS Tahoe 26.5.2. Until patched, restrict web browsing to trusted sites and disable JavaScript if possible.

Recommended fix High confidence

Safari 26.5.2, iOS 26.5.2, iPadOS 26.5.2, macOS Tahoe 26.5.2

  1. Identify the affected Apple product (Safari, iOS, iPadOS, or macOS) that needs to be updated
  2. Check the current version of the product to confirm it is affected (Safari < 26.5.2, iOS < 26.5.2, iPadOS < 26.5.2, or macOS >= 26.0 and < 26.5.2)
  3. For iOS and iPadOS: Go to Settings > General > Software Update and install iOS/iPadOS 26.5.2
  4. For macOS: Go to System Settings > General > Software Update and install macOS Tahoe 26.5.2
  5. For Safari: The Safari update is included with the macOS or iOS update; ensure the OS is updated to receive Safari 26.5.2
  6. After updating, verify the new version is installed

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

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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