Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HSummary
CVE-2025-24139 is a medium-severity Out-of-bounds Write (CWE-787) vulnerability in Apple Macos. Its CVSS base score is 5.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 20th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-16 (Memory Protection) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-24139 is a vulnerability in macOS that allows parsing a maliciously crafted file to lead to an unexpected application termination. The issue, addressed through improved checks, affects macOS versions prior to Sequoia 15.3, Sonoma 14.7.3, Ventura 13.7.3, and Ventura 13.7.5. It carries a CVSS v3.1 base score of 5.5 (medium severity) and is associated with CWE-787 (out-of-bounds write), though additional CWE details are unavailable from NVD.
Exploitation requires local access with low complexity and no privileges, but user interaction is necessary to open the malicious file. A local attacker can achieve high availability impact by causing the targeted application to crash, with no effects on confidentiality or integrity and no scope change.
Apple security advisories, detailed in support pages such as https://support.apple.com/en-us/122068, https://support.apple.com/en-us/122069, https://support.apple.com/en-us/122070, https://support.apple.com/en-us/122375, and http://seclists.org/fulldisclosure/2025/Apr/10, confirm mitigation via updates to the listed macOS versions.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-3647
Vulnerability Data
The issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15.3, macOS Sonoma 14.7.3, macOS Ventura 13.7.3, macOS Ventura 13.7.5. Parsing a maliciously crafted file may lead to an unexpected app termination.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
The vulnerability enables crashing a target application via malicious file parsing (out-of-bounds write leading to termination), directly mapping to application exploitation for denial of service.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Timely flaw remediation through patching directly eliminates the parsing vulnerability in macOS that leads to application crashes from malicious files.
Memory protection mechanisms such as bounds checking prevent out-of-bounds writes during file parsing that cause unexpected app terminations.
Information input validation ensures maliciously crafted files are rejected or sanitized before parsing, mitigating the risk of application crashes.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect and prevent out-of-bounds write defects.
Secure development life cycle mandates practices that prevent out-of-bounds writes.
Application security requirements can specify bounds-checking and safe memory handling.
Secure architecture and engineering principles reduce the likelihood of buffer overflows.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.
Change management can enforce review gates that catch unsafe memory operations before deployment.