CVE-2025-24129 json
A type confusion issue was addressed with improved checks.
published 2025-01-27 21 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-3639
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
A type confusion issue was addressed with improved checks. This issue is fixed in iOS 18.3 and iPadOS 18.3, macOS Sequoia 15.3, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.3, visionOS 2.3. An attacker on the local network may cause an unexpected app termination.
Patch / fix
- Apple iOS and iPadOS 18.3
- Apple macOS 13.7.5, 14.7.5, 15.3
- Apple tvOS 18.3
- Apple visionOS 2.3
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 21 mo ago
Exploit prediction
1.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Apple iOS and iPadOS
- Apple macOS
- Apple tvOS
- Apple visionOS
Classification
- Weakness
-
- CWE-843 Access of Resource Using Incompatible Type
References
-
support.apple.com
/en-us/122066
release-notes, vendor-advisory
-
support.apple.com
/en-us/122068
release-notes, vendor-advisory
-
support.apple.com
/en-us/122072
release-notes, vendor-advisory
-
support.apple.com
/en-us/122073
release-notes, vendor-advisory
- support.apple.com /en-us/122374
- support.apple.com /en-us/122375
- seclists.org /fulldisclosure/2025/Jan/19
- seclists.org /fulldisclosure/2025/Jan/18
- seclists.org /fulldisclosure/2025/Jan/15
- seclists.org /fulldisclosure/2025/Jan/13
- seclists.org /fulldisclosure/2025/Jan/12
Sources
- CVE List CVE-2025-24129
- NVD CVE-2025-24129
Fencer Vulns 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.