CVE-2025-24154 json
An out-of-bounds write was addressed with improved input validation.
published 2025-01-27 21 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-3658
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
An out-of-bounds write was addressed with improved input validation. This issue is fixed in iOS 18.3 and iPadOS 18.3, macOS Sequoia 15.3, macOS Sonoma 14.7.3, macOS Ventura 13.7.3, visionOS 2.3. An attacker may be able to cause unexpected system termination or corrupt kernel memory.
Patch / fix
- Apple iOS and iPadOS 18.3
- Apple macOS 13.7.3, 14.7.3, 15.3
- Apple visionOS 2.3
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 21 mo ago
Exploit prediction
1.16% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
Affected products
- Apple iOS and iPadOS
- Apple macOS
- Apple visionOS
Classification
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/122069
release-notes, vendor-advisory
-
support.apple.com
/en-us/122070
release-notes, vendor-advisory
-
support.apple.com
/en-us/122073
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/13
Sources
- CVE List CVE-2025-24154
- NVD CVE-2025-24154
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.