dbcve.org
SafariWeb browser · Apple

CVE-2026-43713

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 permissions issue was addressed with additional restrictions. This issue is fixed in Safari 26.5.2, iOS 26.5.2 and iPadOS 26.5.2, macOS Tahoe 26.5.2, tvOS 26.6, visionOS 26.6, watchOS 26.6. Visiting a website may leak sensitive data.

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

This is a permissions/access control vulnerability in Apple's Safari browser and multiple operating systems (iOS, iPadOS, macOS, tvOS, visionOS, watchOS). The vulnerability allows a malicious website to potentially leak sensitive data due to insufficient permission restrictions. The fix involves Apple adding additional access restrictions to prevent unauthorized data access via web content.

MitigationUpdate all affected Apple devices to the specified versions (Safari 26.5.2, iOS/iPadOS 26.5.2, macOS Tahoe 26.5.2, tvOS 26.6, visionOS 26.6, watchOS 26.6) or later to apply the vendor patch.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 > About Safari. Compare the version number to the affected range (< 26.5.2).
    Affected if Safari version is less than 26.5.2 on macOS
  2. Check Safari version on iOS/iPadOS
    Open Settings app, go to Safari > About. Compare the version number to the affected range (< 26.5.2).
    Affected if Safari version is less than 26.5.2 on iOS or iPadOS
  3. Check macOS version
    Click Apple menu > About This Mac. The vulnerability applies to macOS >= 26.0 and < 26.5.2.
    Affected if macOS version is 26.0 or higher but Safari is below 26.5.2
  4. Confirm browser is used for web navigation
    The vulnerability triggers when visiting a malicious website. If Safari with a vulnerable version is used for browsing, the permission restriction flaw is present.
    Affected if Safari version is below 26.5.2 and the browser is used to visit websites

A user is affected if their Safari browser version is below 26.5.2 on any Apple platform, or if they are running macOS 26.0-26.5.2 with an unpatched Safari.

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 to the specified versions (Safari 26.5.2, iOS/iPadOS 26.5.2, macOS Tahoe 26.5.2, tvOS 26.6, visionOS 26.6, watchOS 26.6) or later to apply the vendor patch.

Recommended fix High confidence

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

  1. Open the App Store on your Mac (for macOS/Safari) or go to Settings > General > Software Update on iOS/iPadOS devices
  2. For macOS: Check for updates and install macOS Tahoe 26.5.2 when available, or update Safari to 26.5.2
  3. For iOS: Go to Settings > General > Software Update and install iOS 26.5.2
  4. For iPadOS: Go to Settings > General > Software Update and install iPadOS 26.5.2
  5. After updating, verify the installed version in Settings > General > About (iOS/iPadOS) or Safari > About Safari (macOS)

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

Fix this in Safari 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-43713 — 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-43713 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