CVE-2025-43381: 
macOS vulnerability analysis and mitigation

CVE-2025-43381 is a symlink-following vulnerability in the CoreServicesUIAgent component of Apple macOS that allows a malicious app to delete protected user data. It affects macOS Tahoe versions prior to 26.1 and was fixed in macOS Tahoe 26.1, released November 3, 2025. The CVE was published by Apple on December 12, 2025, and received a CVSS v3.1 base score of 5.5 (Medium), assessed by CISA-ADP (Apple Advisory).

The vulnerability is classified as CWE-59 (Improper Link Resolution Before File Access, or 'Link Following'), meaning the affected component fails to properly validate or resolve symbolic links before performing file operations (Apple Advisory). An attacker with a locally installed malicious app (requiring low privileges) can craft a symlink that redirects file deletion operations in CoreServicesUIAgent to target protected user data outside the intended scope. No user interaction is required for exploitation, and the attack is limited to the local system. The fix involved improved handling of symlinks within the CoreServicesUIAgent component. The vulnerability was discovered and reported by Mickey Jin (@patch1t) (Apple Advisory).

Successful exploitation allows a malicious app to delete protected user data on the affected macOS system, resulting in a high integrity impact with no confidentiality or availability impact. The scope is limited to the local machine, and the vulnerability does not enable code execution or privilege escalation on its own. However, targeted deletion of protected data could disrupt user workflows, destroy important files, or be chained with other vulnerabilities for broader impact (Apple Advisory).

1. Develop or deploy a malicious app: Create a macOS application that requires only low (standard user) privileges and can be installed on the target system.
2. Identify target protected data: Determine the path to protected user data that CoreServicesUIAgent is expected to operate on (e.g., files in protected directories managed by the system).
3. Create a malicious symlink: Within the app's accessible file space, create a symbolic link that points to the protected user data path targeted for deletion.
4. Trigger CoreServicesUIAgent file operation: Cause the vulnerable CoreServicesUIAgent component to perform a file deletion operation on the attacker-controlled path, which resolves the symlink and deletes the protected target instead.
5. Achieve impact: The protected user data is deleted without proper authorization, bypassing macOS file protection mechanisms (Apple Advisory).

• File System: Unexpected deletion of files in protected user data directories (e.g., ~/Library subdirectories or system-protected paths); presence of unusual symbolic links in app-writable directories pointing to protected system or user paths.
• Logs: System log entries from CoreServicesUIAgent referencing unexpected file paths or symlink resolution errors; Unified Log entries showing file deletion events initiated by a third-party app via CoreServicesUIAgent.
• Process: Unusual activity from CoreServicesUIAgent process triggered by a sandboxed or low-privilege third-party application; unexpected file system events (e.g., via fs_usage or opensnoop) showing deletion of protected paths by CoreServicesUIAgent.

Apple has addressed this vulnerability in macOS Tahoe 26.1, released November 3, 2025. Users should update to macOS Tahoe 26.1 or later as the primary remediation. No configuration-based workaround has been published; upgrading is the only recommended fix. Organizations should prioritize patching macOS Tahoe systems and review installed third-party applications for suspicious behavior in the interim (Apple Advisory).

The vulnerability was credited to security researcher Mickey Jin (@patch1t), a prolific macOS security researcher known for discovering multiple vulnerabilities in Apple's platform. CVE-2025-43381 was one of numerous security fixes included in the macOS Tahoe 26.1 release, which addressed a broad range of issues across many system components. No significant independent commentary or media coverage specific to this CVE has been identified beyond standard vulnerability tracking (Apple Advisory).