CVE-2025-5469 Dylib Hijacking in Yandex Messenger
High 7.3
Published
Updated
Check this codebase for CVE-2025-5469 and fix it if it is affected.
What it is: CVE-2025-5469 is a high-severity vulnerability in Yandex Messenger, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5469 in the wild and no public exploit code.
Affected product: Yandex Messenger. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2025-5469/ (Markdown: https://insights.sbomify.com/CVE-2025-5469/index.md)
Attackers can execute arbitrary code via dylib hijacking in Yandex Messenger on macOS due to uncontrolled search path elements.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-5469?
CVE-2025-5469 is a high-severity vulnerability in Yandex Messenger, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Uncontrolled Search Path Element vulnerability in Yandex Messenger on MacOS allows Search Order Hijacking.This issue affects Telemost: before 2.245
Weakness: CWE-427
Which versions are affected by CVE-2025-5469?
How do I fix CVE-2025-5469?
No fix has been published for CVE-2025-5469 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-5469 being exploited?
There is no known exploitation of CVE-2025-5469 in the wild and no public exploit code.
Sources
Also known as GHSA-p92j-vq8q-93gg.