Payment-token disclosure via insufficient App Store restrictions
Published Dec 17, 2025 · Updated Dec 17, 2025
Improper access control in the App Store component of Apple operating systems before 26.2 allows attackers to read payment tokens via an app. The App Store permissions layer fails to prevent access by an app, but Apple has not disclosed the affected authorization check or token-access path. Exploitation requires an app to run on an affected device and exposes sensitive payment tokens without reported modification or service interruption.
Summary
What happened
Improper access control in the App Store component of Apple operating systems before 26.2 allows attackers to read payment tokens via an app. The App Store permissions layer fails to prevent access by an app, but Apple has not disclosed the affected authorization check or token-access path. Exploitation requires an app to run on an affected device and exposes sensitive payment tokens without reported modification or service interruption.
The record
- CVE
- CVE-2025-46288
- Published
- Dec 17, 2025
- Updated
- Dec 17, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-284, T1005
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 17, 2025CVE publishedPublication date reported by the CVE source.
- Dec 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <26.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo