Protected filesystem modification via symlink target validation
Published Nov 4, 2025 · Updated Nov 4, 2025
Symlink validation failure in Apple macOS Assets allows local users to modify protected file-system locations through a local app. The Assets component fails to validate a symlink target before performing a file operation, so the link can redirect a write into a protected location. Exploitation requires a locally running app with low user privileges; no public source identifies the affected path or provides a remotely reachable vector.
Summary
What happened
Symlink validation failure in Apple macOS Assets allows local users to modify protected file-system locations through a local app. The Assets component fails to validate a symlink target before performing a file operation, so the link can redirect a write into a protected location. Exploitation requires a locally running app with low user privileges; no public source identifies the affected path or provides a remotely reachable vector.
The record
- CVE
- CVE-2025-43446
- Published
- Nov 4, 2025
- Updated
- Nov 4, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-59, T1565
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 4, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <14.8
- Affected versionversion=unspecified <15.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo