CVE-2026-28929
Apple Macos 14.0 – 14.8.7
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2026-28929 is a high-severity Incorrect Comparison Logic Granularity (CWE-1254) vulnerability in Apple Macos. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Password Guessing (T1110.001); ranked at the 34th 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-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-29246
Vulnerability Data
A logic issue was addressed with improved checks. This issue is fixed in iOS 18.7.9 and iPadOS 18.7.9, macOS Sequoia 15.7.7, macOS Sonoma 14.8.7, macOS Tahoe 26.5. Replying to an email could display remote images in Mail in Lockdown Mode.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V10.4.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can include timing analysis or side-channel tests that reveal stepwise comparison flaws.
Security engineering principles can require constant-time comparison implementations that eliminate stepwise logic.
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 explicitly require constant-time string comparisons, directly preventing the weakness while also covering many other coding issues.
Vulnerability identification processes such as static analysis or code review can discover incorrect-granularity comparisons.
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 can detect timing side-channels arising from stepwise comparison logic.
Secure development lifecycle processes can require constant-time comparison functions to prevent timing side-channels.
Application security requirements can explicitly call for constant-time string comparisons in authentication and cryptographic code.
Secure system architecture principles can mandate constant-time primitives to eliminate timing side-channels.
Secure coding standards can require constant-time comparison functions to avoid stepwise string comparison vulnerabilities.
Secure authentication mechanisms can mandate constant-time comparisons, mitigating timing attacks from stepwise string comparison.