dbcve.org
SafariWeb browser · Apple

CVE-2026-43732

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 path handling issue was addressed with improved validation. 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. Processing maliciously crafted web content may disclose sensitive user information.

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 path handling vulnerability in WebKit allows processing of maliciously crafted web content to disclose sensitive user information. The issue stems from insufficient path validation, likely a path traversal or directory traversal flaw, which was addressed with improved input validation. This affects Safari and WebKit-based browsers across iOS, iPadOS, macOS, tvOS, visionOS, and watchOS.

MitigationUpdate Safari to 26.5.2 or later, and update all affected Apple device operating systems to the specified versions (iOS/iPadOS 26.5.2, macOS Tahoe 26.5.2, tvOS 26.6, visionOS 26.6, watchOS 26.6) to remediate this 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
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, go to Safari menu > About Safari. The version number is displayed next to 'Safari'. Compare it to 26.5.2.
    Affected if The displayed version is earlier than 26.5.2 (for example, 26.5.1, 26.0, 25.x, etc.)
  2. Check iOS version on iPhone
    Open Settings app > General > About. Look for the 'Version' field which shows the iOS version number.
    Affected if The iOS version is earlier than 26.5.2 (for example, 26.5.1, 26.0, 25.x, etc.)
  3. Check iPadOS version on iPad
    Open Settings app > General > About. Look for the 'Version' field which shows the iPadOS version number.
    Affected if The iPadOS version is earlier than 26.5.2 (for example, 26.5.1, 26.0, 25.x, etc.)
  4. Check macOS version
    Click Apple menu > About This Mac. The macOS version is shown below the macOS name (for example, 'macOS Tahoe 26.0' or similar).
    Affected if The macOS version is 26.0 or later but earlier than 26.5.2 (the version will display as something like 26.0, 26.1, 26.2, etc., but not 26.5.2 or later).

You are affected if any device runs Safari, iOS, iPadOS, or macOS with a version number lower than 26.5.2.

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 Safari to 26.5.2 or later, and update all affected Apple device operating systems to the specified versions (iOS/iPadOS 26.5.2, macOS Tahoe 26.5.2, tvOS 26.6, visionOS 26.6, watchOS 26.6) to remediate this vulnerability.

Recommended fix High confidence

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

  1. Open System Preferences (macOS) or Settings (iOS/iPadOS) and check for software updates to install version 26.5.2
  2. For Safari on macOS: Ensure macOS is updated to 26.5.2, which includes Safari 26.5.2
  3. For iOS devices: Go to Settings > General > Software Update and install iOS 26.5.2
  4. For iPadOS devices: Go to Settings > General > Software Update and install iPadOS 26.5.2
  5. For macOS Tahoe: Install the macOS 26.5.2 security update via System Preferences > Software Update

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

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.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-43732 — 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-43732 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