dbcve.org
SafariWeb browser · Apple

CVE-2026-43742

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

A use-after-free vulnerability in WebKit allows processing of maliciously crafted web content to cause an unexpected process crash. This memory management flaw affects Safari and all Apple OS variants running the vulnerable WebKit versions.

MitigationUpdate all affected Apple devices (Safari, iOS, iPadOS, macOS, tvOS, visionOS, watchOS) to the patched versions (26.5.2/26.6 or later) to remediate this client-side vulnerability.

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. Check Safari version on macOS
    Open Safari, click Safari in the menu bar, select About Safari, and note the version number displayed.
    Affected if The version shown is earlier than 26.5.2, or the version shows 26.0 through 26.5.1 (any version less than 26.5.2).
  2. Check iOS Safari version
    Open the Settings app, scroll to Safari, tap Safari, then tap About Safari to view the version number.
    Affected if The displayed version is earlier than 26.5.2.
  3. Check iPadOS Safari version
    Open Settings, go to Safari, then tap About Safari to see the installed version.
    Affected if The version shown is less than 26.5.2.
  4. Check macOS version if using system Safari
    Click the Apple menu in the top-left corner, select About This Mac, and note the macOS version listed.
    Affected if The macOS version is 26.0 or later but earlier than 26.5.2 (any version in the 26.0 to 26.5.1 range).

If any installed Safari, iOS Safari, iPadOS Safari, or macOS Safari browser shows a version lower than 26.5.2, the environment is affected by this use-after-free vulnerability.

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 all affected Apple devices (Safari, iOS, iPadOS, macOS, tvOS, visionOS, watchOS) to the patched versions (26.5.2/26.6 or later) to remediate this client-side vulnerability.

Recommended fix High confidence

Upgrade to Safari 26.5.2, iOS 26.5.2, iPadOS 26.5.2, or macOS Tahoe 26.5.2 as appropriate for your device

  1. Identify the affected Apple device (iPhone, iPad, or Mac running Safari)
  2. On iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 26.5.2
  3. On macOS: Go to System Settings > General > Software Update and install macOS Tahoe 26.5.2
  4. After updating the operating system, Safari will automatically be updated to 26.5.2
  5. Verify the update was successful by checking Safari version (Safari > About Safari) or iOS/iPadOS version (Settings > General > About)
Caveat Standard Apple OS update considerations - ensure backups before updating, some older apps may not be compatible with new OS versions

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

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Review / QA1.0 h
2.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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