dbcve.org
SafariWeb browser · Apple

CVE-2026-43663

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 allows malicious web content to cause an unexpected process crash in Safari and other Apple web rendering components. This is a denial-of-service flaw in the memory management of WebKit's handling of crafted web content.

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, watchOS 26.6) to all affected Apple devices.

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. Identify the platform and product
    Determine if the device is running Safari on macOS, iOS, iPadOS, or macOS Tahoe. On macOS, open Safari and go to Safari > About Safari. On iOS/iPadOS, go to Settings > General > About to view the iOS/iPadOS version.
    Affected if The device runs any of the affected products (Safari, iOS, iPadOS, or macOS) and the version is below 26.5.2
  2. Check Safari version on macOS
    Open Safari and select Safari > About Safari. Note the version number displayed (e.g., 26.5.1 or earlier).
    Affected if The displayed version is less than 26.5.2
  3. Check iOS version on iPhone
    On iPhone, go to Settings > General > About and note the iOS version number.
    Affected if The iOS version is less than 26.5.2
  4. Check iPadOS version on iPad
    On iPad, go to Settings > General > About and note the iPadOS version number.
    Affected if The iPadOS version is less than 26.5.2
  5. Check macOS Tahoe version
    On macOS, go to System Settings > General > About to view the macOS version. Note that macOS Tahoe is the affected product.
    Affected if The macOS version (Tahoe) is less than 26.5.2

The environment is affected if any Safari, iOS, iPadOS, or macOS Tahoe installation is found with a version number lower than 26.5.2.

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, watchOS 26.6) to all affected Apple devices.

Recommended fix High confidence

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

  1. For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 26.5.2
  2. For macOS: Open System Settings > General > Software Update and install macOS Tahoe 26.5.2
  3. For Safari: Updating macOS will automatically update Safari to 26.5.2; iOS/iPadOS Safari updates with the OS update
  4. After updating, restart the device to ensure all security patches are fully applied
Caveat Apple minor version updates typically have no breaking changes; however, ensure backups exist before updating

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

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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