SafariWeb browser · Apple
CVE-2025-43502
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 · uneditedA privacy issue was addressed by removing sensitive data. This issue is fixed in Safari 26.1, iOS 26.1 and iPadOS 26.1, macOS Tahoe 26.1, visionOS 26.1. An app may be able to bypass certain Privacy preferences.
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 confidenceThis is a privacy bypass vulnerability in Apple operating systems where an app could bypass certain Privacy preferences. The fix involved removing sensitive data that was being exposed. The specific mechanism of bypass and nature of sensitive data are not detailed in the available advisory.
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
< 26.1< 26.1< 26.1< 26.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Safari version on macOSOpen Safari, go to Safari menu > About Safari. Note the version number shown.Affected if Version shown is earlier than 26.1, or the 'About Safari' window does not display a version (indicating an older unpatched build).
-
Check iOS version on iPhoneOpen Settings app > General > About. Note the 'Version' field showing the iOS release number.Affected if Version number is earlier than 26.1 (for example, 26.0.x or any 25.x release).
-
Check iPadOS version on iPadOpen Settings app > General > About. Note the 'Version' field showing the iPadOS release number.Affected if Version number is earlier than 26.1.
-
Check visionOS version on Apple VisionOpen Settings app > General > About. Note the 'Version' field showing the visionOS release number.Affected if Version number is earlier than 26.1.
You are affected if any Safari, iOS, iPadOS, or visionOS device in your environment runs a version lower than 26.1, as the privacy preference bypass vulnerability exists in those earlier releases.
Generated from the published advisory. Verify against your own configuration.
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 · scoped26.1
Update to Safari 26.1, iOS 26.1, iPadOS 26.1, macOS Tahoe 26.1, or visionOS 26.1 to apply the fix that removes the sensitive data enabling the privacy preference bypass.
iOS 26.1, iPadOS 26.1, Safari 26.1, visionOS 26.1, macOS Tahoe 26.1
- Open Settings on iPhone or iPad
- Tap General, then tap Software Update
- Download and install iOS 26.1 or iPadOS 26.1
- For Safari users on macOS, open System Settings > General > Software Update and install macOS Tahoe 26.1
- For visionOS users, go to Settings > General > Software Update and install visionOS 26.1
- After updating, verify the fix by checking that apps can no longer bypass Privacy preferences in Settings
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Safari
Scoped from the published advisory
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-43502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-43502 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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