Local code execution via uncontrolled dylib search
Published Dec 9, 2025 · Updated Dec 9, 2025
Uncontrolled search path handling in Yandex Messenger before 2.245 allows local users to execute code through dylib hijacking. Yandex identifies the macOS desktop application's dynamic-library search order as uncontrolled but has not disclosed the library, path element, or load operation involved. Exploitation requires low-privileged local access and an unspecified additional condition, after which attacker-supplied code runs in the application's context.
Summary
What happened
Uncontrolled search path handling in Yandex Messenger before 2.245 allows local users to execute code through dylib hijacking. Yandex identifies the macOS desktop application's dynamic-library search order as uncontrolled but has not disclosed the library, path element, or load operation involved. Exploitation requires low-privileged local access and an unspecified additional condition, after which attacker-supplied code runs in the application's context.
The record
- CVE
- CVE-2025-5469
- Published
- Dec 9, 2025
- Updated
- Dec 9, 2025
- Vendor
- Yandex
- Product
- Yandex Messenger
- Classifications
- CWE-427, CAPEC-471, T1574.006
- 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 <2.245
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