User fingerprinting via Call History data exposure
Published Sep 15, 2025 · Updated Sep 15, 2025
Information disclosure in Apple iOS, iPadOS, and macOS allows attackers to fingerprint users through exposed Call History data. The Call History component fails to fully redact sensitive information before making it available to apps, exposing user-linked signals. A locally installed app and user interaction are required; the exposed fields and affected API path remain undisclosed.
Summary
What happened
Information disclosure in Apple iOS, iPadOS, and macOS allows attackers to fingerprint users through exposed Call History data. The Call History component fails to fully redact sensitive information before making it available to apps, exposing user-linked signals. A locally installed app and user interaction are required; the exposed fields and affected API path remain undisclosed.
The record
- CVE
- CVE-2025-43357
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-359
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 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
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.
Weakness, pattern, technique
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