dbcve.org
SafariWeb browser · Apple

CVE-2026-43794

HIGH · 8.8 CVSS v3.1 Developing Published 2026-08-17
Fix available
A fix is available. Upgrade to 18.7.10 / 26.6.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Brand new

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 memory corruption issue was addressed with improved memory handling. This issue is fixed in Safari 26.6.1, iOS 18.7.10 and iPadOS 18.7.10, iOS 26.6.1 and iPadOS 26.6.1, macOS Tahoe 26.6.2. Processing maliciously crafted web content may lead to memory corruption.

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-31.

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.6.1
IpadosOperating system
Affected:< 18.7.10>= 26.0, < 26.6.1
Iphone OsOperating system
Affected:< 18.7.10>= 26.0, < 26.6.1
macOSOperating system
Affected:>= 26.0, < 26.6.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 18.7.10 / 26.6.1 / 26.6.2 or later
Fixed in 18.7.1026.6.126.6.2
Recommended fix High confidence

Safari 26.6.1 / iOS 18.7.10 / iPadOS 18.7.10 / iOS 26.6.1 / iPadOS 26.6.1 / macOS Tahoe 26.6.2

  1. Identify the affected Apple product (Safari, iOS, iPadOS, or macOS) running on the system
  2. Check the current version of the affected software in Settings > General > About (iOS/iPadOS) or Safari > About Safari (macOS)
  3. For Safari on any platform: Upgrade to Safari 26.6.1 or later
  4. For iOS: Upgrade to iOS 18.7.10 or later (or iOS 26.6.1 for newer devices)
  5. For iPadOS: Upgrade to iPadOS 18.7.10 or later (or iPadOS 26.6.1 for newer devices)
  6. For macOS: Upgrade to macOS Tahoe 26.6.2 or later
  7. Restart the device after updating to ensure the fix is fully applied
Caveat Standard Apple update compatibility applies; older devices may not support the latest OS versions

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $8,000. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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