dbcve.org
SafariWeb browser · Apple

CVE-2026-43721

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
This issue was addressed through improved state management. 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. A malicious website may be able to silently hijack clipboard 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 · moderate confidence

A vulnerability in WebKit allows malicious websites to silently access and modify clipboard data due to improper state management. An attacker could read sensitive information from the clipboard (such as passwords, tokens, or personal data) or overwrite clipboard contents without user interaction or awareness.

MitigationApply the available security updates: Safari 26.5.2, iOS 26.5.2 and iPadOS 26.5.2, macOS Tahoe 26.5.2, tvOS 26.6, visionOS 26.6, or watchOS 26.6. Organizations should ensure all managed Apple devices are updated to these versions or later.

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. Identify the Safari browser version on macOS
    Open Safari, go to Safari menu > About Safari. The version number is displayed next to 'Safari'.
    Affected if version number is less than 26.5.2
  2. Identify the iOS version on iPhone
    Open Settings app > General > About. The version number is displayed under 'Version'.
    Affected if version number is less than 26.5.2
  3. Identify the iPadOS version on iPad
    Open Settings app > General > About. The version number is displayed under 'Version'.
    Affected if version number is less than 26.5.2
  4. Identify the macOS version if Safari is bundled
    Open System Settings (or System Preferences) > General > About. The version number is displayed under 'macOS'.
    Affected if macOS version is 26.0 or higher but less than 26.5.2

You are affected if any Apple device runs Safari, iOS, iPadOS, or macOS versions prior to 26.5.2, as those versions contain the improper state management that allows malicious websites to read clipboard data without user interaction.

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 available security updates: Safari 26.5.2, iOS 26.5.2 and iPadOS 26.5.2, macOS Tahoe 26.5.2, tvOS 26.6, visionOS 26.6, or watchOS 26.6. Organizations should ensure all managed Apple devices are updated to these versions or later.

Recommended fix High confidence

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

  1. For Safari on macOS: Open the App Store, click Updates, find Safari 26.5.2, and click Update
  2. For iOS devices: Open Settings > General > Software Update, then download and install iOS 26.5.2
  3. For iPadOS devices: Open Settings > General > Software Update, then download and install iPadOS 26.5.2
  4. For macOS: Open System Settings > General > Software Update, then download and install macOS Tahoe 26.5.2
  5. After updating, restart your device to ensure the clipboard security fix is fully applied

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

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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