Cyber Resilience

CVE-2025-24210

Apple Macos 13.0 – 13.7.5

Published
31 March 2025
Modified
02 April 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0031 23th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

CVE-2025-24210 is a medium-severity Operator Precedence Logic Error (CWE-783) vulnerability in Apple Macos. Its CVSS base score is 5.5 (Medium).

Operationally, ranked at the 23th 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 SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A logic error was addressed with improved error handling. This issue is fixed in iOS 18.4 and iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, visionOS 2.4, watchOS 11.4. Parsing an image may…

more

lead to disclosure of user information.

CWE(s)
CWE-783

Related Threats

CVEs Like This One

CVE-2025-30445Same product: Apple Ipados
CVE-2025-31197Same product: Apple Ipados
CVE-2025-30447Same product: Apple Ipados
CVE-2025-24179Same product: Apple Ipados
CVE-2025-30471Same product: Apple Ipados
CVE-2024-27831Same product: Apple Ipados
CVE-2025-24271Same product: Apple Ipados
CVE-2025-43385Same product: Apple Ipados
CVE-2025-24212Same product: Apple Ipados
CVE-2025-24270Same product: Apple Ipados

Affected Assets

apple
ipados
≤ 17.7.6 · 18.0 — 18.4
apple
iphone os
≤ 18.4
apple
macos
13.0 — 13.7.5 · 14.0 — 14.7.5 · 15.0 — 15.4
apple
tvos
≤ 18.4
apple
visionos
≤ 2.4

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and static analysis directly find incorrect evaluation results caused by precedence mistakes.

SA-15 Development Process, Standards, and Tools partial match

Documented development standards and coding rules can require constructs that eliminate ambiguous operator precedence.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can mandate explicit parentheses and precedence rules that structurally prevent the logic error from being written.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices (reviews, static analysis, testing) directly catch precedence errors while the control also addresses many other development risks.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect logic errors caused by precedence issues.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes code review and testing that can catch precedence errors.

A.8.28 Secure coding partial match
prevents

Secure coding standards and guidelines directly address operator precedence mistakes.

References