Local code execution via uncontrolled dylib search path
Published Dec 9, 2025 · Updated Dec 9, 2025
Uncontrolled search path handling in Yandex Disk before 3.2.45.3275 allows local users to execute code through dylib hijacking. The Yandex disclosure does not identify the affected executable, library, or search-path entry; it states only that the macOS app uses an uncontrolled search path. Exploitation requires local low-privileged access and a prerequisite condition; successful hijacking executes attacker-controlled code in the application's context.
Summary
What happened
Uncontrolled search path handling in Yandex Disk before 3.2.45.3275 allows local users to execute code through dylib hijacking. The Yandex disclosure does not identify the affected executable, library, or search-path entry; it states only that the macOS app uses an uncontrolled search path. Exploitation requires local low-privileged access and a prerequisite condition; successful hijacking executes attacker-controlled code in the application's context.
The record
- CVE
- CVE-2025-5470
- Published
- Dec 9, 2025
- Updated
- Dec 9, 2025
- Vendor
- Yandex
- Product
- Yandex Disk
- Classifications
- CWE-427, CAPEC-471, T1574.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- Dec 9, 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=0 <3.2.45.3275
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