CVE-2025-43298
Apple Macos 14.0 – 14.8
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-43298 is a high-severity Improper Resolution of Path Equivalence (CWE-41) vulnerability in Apple Macos. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 13th 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 AC-3 (Access Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-29272
Vulnerability Data
A parsing issue in the handling of directory paths was addressed with improved path validation. This issue is fixed in macOS Sequoia 15.7, macOS Sonoma 14.8, macOS Tahoe 26. An app may be able to gain root privileges.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation of file paths directly rejects or normalizes the special-character manipulations that create equivalent names.
Proper enforcement of file access authorizations structurally blocks disclosure when equivalent paths are presented.
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.
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.
Secure coding standards directly require canonical path resolution and input sanitization to prevent equivalence attacks.
Security testing can detect path-equivalence flaws before release, partially fulfilling the control.
Secure development lifecycle includes path-handling requirements that reduce equivalence-based disclosure.
Application security requirements can mandate canonicalization and input validation to block path equivalence.
Secure architecture principles call for safe file-system abstractions that mitigate path traversal risks.
Information access restriction limits what files can be reached, indirectly reducing impact of path-equivalence exploits.