CVE-2025-5469
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUncontrolled Search Path Element vulnerability in Yandex Messenger on MacOS allows Search Order Hijacking.This issue affects Telemost: before 2.245
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceYandex Messenger Telemost on macOS before version 2.245 contains an Uncontrolled Search Path Element vulnerability allowing Search Order Hijacking. An attacker could place a malicious dynamic library in a directory that is searched before the legitimate library location, causing the application to load the malicious code when launched.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- Authentication
- Y
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:A/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Find installed Yandex Messenger Telemost versionRun: mdls -name kCFBundleShortVersionString /Applications/Yandex\ Messenger\ Telemost.app/Contents/Info.plist 2>/dev/null || grep -A1 CFBundleShortVersionString /Applications/Yandex\ Messenger\ Telemost.app/Contents/Info.plistAffected if Version returned is lower than 2.245 or no version info is found (app may be pre-2.245)
-
Verify application install locationRun: ls -la /Applications/Yandex\ Messenger\ Telemost.app/ or ls -la ~/Applications/Yandex\ Messenger\ Telemost.app/ 2>/dev/nullAffected if Application is installed in user-writable directories like ~/Applications/ instead of /Applications/ (trusted system directory)
-
Check application bundle for unexpected dylib filesRun: find /Applications/Yandex\ Messenger\ Telemost.app/Contents -name '*.dylib' -type f 2>/dev/nullAffected if Any unexpected or suspicious dynamic library files exist within the application bundle that are not part of the official release
-
Inspect application directory for pre-existing malicious librariesCheck the parent directory of the app for any .dylib files: ls -la /Applications/*.dylib 2>/dev/null or ls -la ~/*.dylib 2>/dev/null if app is in user directoryAffected if Any untrusted .dylib files exist in directories that would be searched before the legitimate library location when the app launches
You are affected if Yandex Messenger Telemost version is below 2.245 AND the app is running from a non-trusted directory OR suspicious dynamic libraries exist in paths searched before the legitimate library location.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Yandex Messenger Telemost to version 2.245 or later. If upgrade is not immediately possible, ensure the application runs from trusted directories and verify no untrusted libraries exist in paths that precede legitimate library locations.
Telemost 2.245 or later
- Check the current version of Yandex Messenger (Telemost) installed on the macOS system
- Update Yandex Messenger (Telemost) to version 2.245 or later to resolve the Search Order Hijacking vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5469 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-5469 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data