dbcve.org
IpadosOperating system · Apple

CVE-2025-46288

MEDIUM · 5.5 CVSS v3.1 Published 2025-12-17
Fix available
A fix is available. Upgrade to 26.2 or later.
See remediation →
57/100
Remediation priority · Elevated
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 permissions issue was addressed with additional restrictions. This issue is fixed in iOS 26.2 and iPadOS 26.2, macOS Tahoe 26.2, visionOS 26.2, watchOS 26.2. An app may be able to access sensitive payment tokens.

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 permissions vulnerability in Apple operating systems allowed an application to access sensitive payment tokens due to insufficient access restrictions. The fix implements additional permission controls to properly isolate payment token data.

MitigationApply the available OS updates (iOS 26.2, iPadOS 26.2, macOS Tahoe 26.2, visionOS 26.2, watchOS 26.2) to devices within the affected fleet. Note: The version numbers listed in the advisory appear atypical and should be verified against Apple's official release notes.

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.2
Iphone OsOperating system
Affected:< 26.2
macOSOperating system
Affected:< 26.2
VisionosOperating system
Affected:< 26.2
WatchosOperating system
Affected:< 26.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 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 and look at the 'Version' field, or run 'nsurlsessiond -v' in Terminal to query the installed iOS version
    Affected if The version number is less than 26.2 (for example, 26.1, 25.x, or earlier)
  2. Check iPadOS version on iPad
    Go to Settings > General > About on the iPad and look at the 'Version' field, or run 'sw_vers' in Terminal to query the installed iPadOS version
    Affected if The version number is less than 26.2 (for example, 26.1, 25.x, or earlier)
  3. Check macOS version on Mac
    Click the Apple menu > About This Mac, or run 'sw_vers' in Terminal to query the installed macOS version
    Affected if The version number is less than 26.2 (for example, 26.1, 25.x, or earlier)
  4. Check visionOS version on Apple Vision
    Go to Settings > General > About on the Apple Vision device and look at the 'Version' field
    Affected if The version number is less than 26.2 (for example, 26.1, 25.x, or earlier)
  5. Check watchOS version on Apple Watch
    On the Apple Watch, go to Settings > General > About and note the watchOS version, or check via the paired iPhone in Watch app > General > About
    Affected if The version number is less than 26.2 (for example, 26.1, 25.x, or earlier)

A device is affected if it runs any of the listed Apple operating systems with a version number lower than 26.2, as the vulnerability exists in versions before the fix that added proper permission controls for payment token isolation.

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.2 or later
Fixed in 26.2
Interim mitigation

Apply the available OS updates (iOS 26.2, iPadOS 26.2, macOS Tahoe 26.2, visionOS 26.2, watchOS 26.2) to devices within the affected fleet. Note: The version numbers listed in the advisory appear atypical and should be verified against Apple's official release notes.

Recommended fix High confidence

iOS 26.2, iPadOS 26.2, macOS Tahoe 26.2, watchOS 26.2, or visionOS 26.2 depending on device

  1. Identify the affected Apple device (iPhone, iPad, Mac, Apple Watch, or Apple Vision Pro)
  2. Check the current OS version on the device
  3. For iPhone: Upgrade to iOS 26.2
  4. For iPad: Upgrade to iPadOS 26.2
  5. For Mac: Upgrade to macOS Tahoe 26.2
  6. For Apple Watch: Upgrade to watchOS 26.2
  7. For Apple Vision Pro: Upgrade to visionOS 26.2
  8. Install the update via Settings > General > Software Update (iOS/iPadOS/watchOS/visionOS) or System Settings > General > Software Update (macOS)
Caveat Standard Apple OS update - review release notes for any app compatibility changes

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

Fix this in Ipados 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-46288 — 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-2025-46288 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