dbcve.org
IpadosOperating system · Apple

CVE-2026-43658

HIGH · 7.5 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 26.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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, iOS 18.7.10 and iPadOS 18.7.10, iOS 26.5 and iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, watchOS 26.5. 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 · high confidence

A memory handling vulnerability in WebKit allows malicious web content to cause an unexpected Safari crash. The vulnerability is triggered when a user processes crafted HTML/JavaScript content, leading to memory corruption that results in a denial-of-service condition.

MitigationApply the vendor-supplied updates (Safari 26.5, iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, watchOS 26.5) to all affected devices. Until patched, restrict user access to untrusted websites.

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
IpadosOperating system
Affected:< 26.5
Iphone OsOperating system
Affected:< 26.5
macOSOperating system
Affected:>= 26.0, < 26.5
TvosOperating system
Affected:< 26.5
VisionosOperating system
Affected:< 26.5
WatchosOperating system
Affected:< 26.5

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

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

  1. Check Safari version on macOS
    Open Safari, click Safari menu, select About Safari. Note the version number displayed.
    Affected if Version is 26.0 or higher but lower than 26.5 (26.0 <= version < 26.5)
  2. Check iOS or iPadOS version
    Open Settings app, go to General > About. Note the iOS version number.
    Affected if iOS or iPadOS version is lower than 26.5 (version < 26.5)
  3. Check tvOS version
    Open Settings app on Apple TV, go to General > About. Note the tvOS version number.
    Affected if tvOS version is lower than 26.5 (version < 26.5)
  4. Check visionOS version
    Open Settings app on Vision Pro, go to General > About. Note the visionOS version number.
    Affected if visionOS version is lower than 26.5 (version < 26.5)
  5. Check watchOS version
    Open Settings app on Apple Watch, go to General > About. Note the watchOS version number.
    Affected if watchOS version is lower than 26.5 (version < 26.5)

The environment is affected if any Apple OS (iOS, iPadOS, macOS 26.0+, tvOS, visionOS, watchOS) is running a version lower than 26.5, since the vulnerability exists in the Safari web rendering engine included with these OS versions.

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

Apply the vendor-supplied updates (Safari 26.5, iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, watchOS 26.5) to all affected devices. Until patched, restrict user access to untrusted websites.

Recommended fix High confidence

Upgrade to iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, or watchOS 26.5 (and corresponding Safari 26.5)

  1. Identify the affected Apple device (iPhone, iPad, Mac, Apple TV, Apple Vision Pro, or Apple Watch)
  2. Determine the current OS version by going to Settings > General > About (iOS/iPadOS) or System Settings > General > About (macOS)
  3. Back up the device before updating
  4. Update to iOS 26.5 or later for iPhone devices
  5. Update to iPadOS 26.5 or later for iPad devices
  6. Update to macOS Tahoe 26.5 or later for Mac computers
  7. Update to tvOS 26.5 or later for Apple TV devices
  8. Update to visionOS 26.5 or later for Apple Vision Pro devices
Caveat Standard OS update; ensure backup before upgrading

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

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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