Cyber Resilience

CVE-2025-43220

Apple Macos ≤ 13.7.7

Published
30 July 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0083 54th percentile
Risk Priority 73 floored blend · peak EPSS

Summary

CVE-2025-43220 is a critical-severity Link Following (CWE-59) vulnerability in Apple Macos. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — 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-43220 is a symlink validation flaw (CWE-59) affecting Apple platforms prior to iPadOS 17.7.9, macOS Sequoia 15.6, macOS Sonoma 14.7.7, and macOS Ventura 13.7.7. The vulnerability stems from insufficient checks on symbolic links, which can allow unauthorized traversal to protected user data locations.

An unauthenticated attacker can exploit the issue over the network with low complexity and no user interaction, achieving full confidentiality, integrity, and availability impact by accessing or modifying protected files that an application should not reach.

Apple security advisories for the listed updates state that the issue is resolved through improved symlink validation; organizations should apply the patches available at the referenced support.apple.com URLs to eliminate the exposure. The associated EPSS score has remained flat at 0.01 with no material increase since disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

This issue was addressed with improved validation of symlinks. This issue is fixed in iPadOS 17.7.9, macOS Sequoia 15.6, macOS Sonoma 14.7.7, macOS Ventura 13.7.7. An app may be able to access protected user data.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1034 Path Interception Persistence
**This technique has been deprecated.
T1547.009 Shortcut Modification Persistence
Adversaries may create or modify shortcuts that can execute a program during system boot or user login.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-28866Same product: Apple Ipados
CVE-2024-44131Same product: Apple Ipados
CVE-2025-43446Same product: Apple Macos
CVE-2025-24278Same product: Apple Macos
CVE-2025-46293Same product: Apple Macos
CVE-2025-43395Same product: Apple Macos
CVE-2024-54554Same product: Apple Macos
CVE-2025-24136Same product: Apple Macos
CVE-2023-42844Same product: Apple Macos
CVE-2025-31198Same product: Apple Macos

Affected Assets

apple
ipados
≤ 17.7.9
apple
macos
≤ 13.7.7 · 14.0 — 14.7.7 · 15.0 — 15.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V15.4.2

Mitigating Controls (NIST 800-53 r5) AI

Proper enforcement of access authorizations on the resolved target resource stops a link from reaching an unintended object.

Least-privilege limits the damage an attacker can cause after following an unintended link.

Validating file-name inputs can reject or canonicalize names that resolve to links before access occurs.

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 directly require code to validate paths and avoid unsafe link following.

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.

finds

Security testing can detect link-following flaws before release.

prevents

Secure SDLC practices can mandate link-resolution checks and canonicalization before file access.

prevents

Application security requirements can explicitly require safe handling of symbolic links and path traversal.

prevents

Secure architecture principles include input validation and safe file-access design patterns.

prevents

Secure coding standards directly address canonicalization and symlink attacks during implementation.

mitigates

Access-control rules can limit which files are reachable, reducing exposure to malicious links.

References