SafariWeb browser · Apple

CVE-2025-43480

HIGH · 8.1 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to 26.1 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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
The issue was addressed with improved checks. This issue is fixed in Safari 26.1, iOS 26.1 and iPadOS 26.1, macOS Tahoe 26.1, tvOS 26.1, visionOS 26.1, watchOS 26.1. A malicious website may exfiltrate data cross-origin.

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

This is a cross-origin data exfiltration vulnerability in WebKit/Apple's browser engine. A malicious website can bypass Same-Origin Policy checks to steal sensitive data from other origins. The issue was addressed with improved origin validation checks in the patched versions.

MitigationUpdate affected Apple products to the fixed versions: Safari 26.1, iOS 26.1, iPadOS 26.1, macOS Tahoe 26.1, tvOS 26.1, visionOS 26.1, and watchOS 26.1.

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.1
IpadosOperating system
Affected:< 26.1
Iphone OsOperating system
Affected:< 26.1
TvosOperating system
Affected:< 26.1
VisionosOperating system
Affected:< 26.1
WatchosOperating system
Affected:< 26.1

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 > About Safari, or run 'defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString' in Terminal
    Affected if The displayed version is lower than 26.1
  2. Check iOS version on iPhone
    Go to Settings > General > About > Version on the iPhone device
    Affected if The version number is lower than 26.1
  3. Check iPadOS version on iPad
    Go to Settings > General > About > Version on the iPad device
    Affected if The version number is lower than 26.1
  4. Check tvOS version on Apple TV
    Go to Settings > General > About > Version on the Apple TV device
    Affected if The version number is lower than 26.1
  5. Check visionOS version on Vision Pro
    Go to Settings > General > About > Version in the Vision Pro device
    Affected if The version number is lower than 26.1
  6. Check watchOS version on Apple Watch
    Open the Watch app on paired iPhone, go to My Watch > General > About, or go to Settings > General > About on the Watch itself
    Affected if The version number is lower than 26.1

You are affected if any Safari, iOS, iPadOS, tvOS, visionOS, or watchOS device in your environment runs a version lower than 26.1 and can access untrusted websites.

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.1 or later
Fixed in 26.1
Interim mitigation

Update affected Apple products to the fixed versions: Safari 26.1, iOS 26.1, iPadOS 26.1, macOS Tahoe 26.1, tvOS 26.1, visionOS 26.1, and watchOS 26.1.

Recommended fix High confidence

Safari 26.1, iOS 26.1, iPadOS 26.1, tvOS 26.1, visionOS 26.1, watchOS 26.1, macOS Tahoe 26.1

  1. Upgrade Safari to version 26.1 or later
  2. Upgrade iOS devices to iOS 26.1 or later
  3. Upgrade iPadOS devices to iPadOS 26.1 or later
  4. Upgrade Apple TV devices to tvOS 26.1 or later
  5. Upgrade Apple Vision Pro devices to visionOS 26.1 or later
  6. Upgrade Apple Watch devices to watchOS 26.1 or later
  7. For macOS systems, upgrade to macOS Tahoe 26.1 or later (if applicable)

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-2025-43480 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-43480 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