Cyber Resilience

CVE-2024-27886

Apple Macos 14.0 – 14.4

Published
29 July 2024
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:N/UI:R/S:U/C:N/I:H/A:N
EPSS Score 0.0048 39th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2024-27886 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 39th 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 issue was addressed with improved restrictions. This issue is fixed in macOS Sonoma 14.4, macOS Ventura 13.7. An unprivileged app may be able to log keystrokes in other apps including those using secure input mode.

CWE(s)
NVD-CWE-noinfoCWE-783

Related Threats

CVEs Like This One

CVE-2024-27888Same product: Apple Macos
CVE-2025-43499Same product: Apple Macos
CVE-2024-44163Same product: Apple Macos
CVE-2024-40861Same product: Apple Macos
CVE-2024-40801Same product: Apple Macos
CVE-2023-28195Same product: Apple Macos
CVE-2025-43446Same product: Apple Macos
CVE-2025-43322Same product: Apple Macos
CVE-2025-43197Same product: Apple Macos
CVE-2024-27824Same product: Apple Macos

Affected Assets

apple
macos
14.0 — 14.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