IpadosOperating system · Apple

CVE-2025-43507

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to 26.1 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 privacy issue was addressed by moving sensitive data. This issue is fixed in iOS 18.7.2 and iPadOS 18.7.2, iOS 26.1 and iPadOS 26.1, macOS Tahoe 26.1, visionOS 26.1, watchOS 26.1. An app may be able to fingerprint the user.

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 privacy bypass vulnerability affecting multiple Apple operating systems (iOS, iPadOS, macOS, visionOS, watchOS). The issue allowed applications to fingerprint users - enabling tracking of users across sessions without consent by accessing sensitive data that should have been protected. Apple addressed it by moving sensitive data to prevent user identification.

MitigationUsers should update their devices to the fixed versions: iOS 18.7.2/iPadOS 18.7.2 or iOS 26.1/iPadOS 26.1, macOS Tahoe 26.1, visionOS 26.1, and watchOS 26.1. No application code changes are required as this is an OS-level fix.

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
IpadosOperating system
Affected:< 26.1
Iphone OsOperating 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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 iOS version on iPhone
    Go to Settings > General > About on the iPhone device and note the version number listed next to 'Software Version'
    Affected if The version number is lower than 26.1 (for example, 18.x, 17.x)
  2. Check iPadOS version on iPad
    Go to Settings > General > About on the iPad device and note the version number listed next to 'Software Version'
    Affected if The version number is lower than 26.1 (for example, 18.x, 17.x)
  3. Check visionOS version on Apple Vision
    Go to Settings > General > About on the Apple Vision device and note the version number listed next to 'Software Version'
    Affected if The version number is lower than 26.1 (for example, 1.x)
  4. Check watchOS version on Apple Watch
    Open the Watch app on the paired iPhone, go to My Watch > General > About, and note the version number; alternatively, go to Settings > General > About on the Apple Watch itself
    Affected if The version number is lower than 26.1 (for example, 11.x, 10.x)

A user is affected if any of their devices (iPhone, iPad, Apple Vision, or Apple Watch) run an OS version lower than 26.1, as older versions allow applications to access sensitive data for user fingerprinting without consent.

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

Users should update their devices to the fixed versions: iOS 18.7.2/iPadOS 18.7.2 or iOS 26.1/iPadOS 26.1, macOS Tahoe 26.1, visionOS 26.1, and watchOS 26.1. No application code changes are required as this is an OS-level fix.

Recommended fix Moderate confidence

iOS 26.1, iPadOS 26.1, visionOS 26.1, watchOS 26.1 (or iOS 18.7.2/iPadOS 18.7.2 for 18.x branches)

  1. Upgrade iPhone to iOS 26.1 or later
  2. Upgrade iPad to iPadOS 26.1 or later
  3. Upgrade Apple Vision to visionOS 26.1 or later
  4. Upgrade Apple Watch to watchOS 26.1 or later
  5. Alternatively, for iOS/iPadOS 18.x branches, upgrade to iOS 18.7.2/iPadOS 18.7.2 or later
Caveat Standard iOS upgrade considerations apply - ensure device backup before upgrading, review app compatibility

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

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.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-2025-43507 — 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-43507 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