CVE-2025-24102 json
The issue was addressed with improved checks.
published last yr. modified 4mo ago also EUVD-2025-3617
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
The issue was addressed with improved checks. This issue is fixed in iPadOS 17.7.4, macOS Sequoia 15.3, macOS Sonoma 14.7.3, macOS Ventura 13.7.3. An app may be able to determine a user’s current location.
Patch / fix
- Apple iPadOS 17.7.4
- Apple macOS 13.7.3, 14.7.3, 15.3
Is CVE-2025-24102 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.95% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Apple iPadOS
- Apple macOS
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
support.apple.com
/en-us/122067
release-notes, vendor-advisory
-
support.apple.com
/en-us/122068
release-notes, vendor-advisory
-
support.apple.com
/en-us/122069
release-notes, vendor-advisory
-
support.apple.com
/en-us/122070
release-notes, vendor-advisory
- seclists.org /fulldisclosure/2025/Jan/17
- seclists.org /fulldisclosure/2025/Jan/16
- seclists.org /fulldisclosure/2025/Jan/15
- seclists.org /fulldisclosure/2025/Jan/14
Sources
- CVE List CVE-2025-24102
- NVD CVE-2025-24102
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.