dbcve.org
Yandex TelemostApplication · Yandex

CVE-2025-5471

HIGH · 7.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 2.19.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Uncontrolled Search Path Element vulnerability in Yandex Telemost on MacOS allows Search Order Hijacking.This issue affects Telemost: before 2.19.1.

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 · high confidence

Yandex Telemost on macOS versions before 2.19.1 contains an Uncontrolled Search Path Element vulnerability allowing Search Order Hijacking. The application loads dynamic libraries (dylibs) from locations an attacker can control, potentially executing malicious code by placing a crafted library in a directory searched before legitimate locations.

MitigationUpgrade Yandex Telemost to version 2.19.1 or later. Until upgraded, ensure the application runs from trusted directories and avoid running from locations with untrusted write access (e.g., downloaded folders, external drives).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Yandex TelemostApplication
Affected:< 2.19.1

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Yandex Telemost is installed
    Open Finder, go to /Applications folder, and look for 'Yandex Telemost.app'. Alternatively, run: ls /Applications | grep -i telemost
    Affected if Yandex Telemost.app exists in /Applications or other locations
  2. Determine the installed version
    Right-click Yandex Telemost.app, select 'Get Info', and check the version number under 'General'. Or run: defaults read /Applications/Yandex\ Telemost.app/Contents/Info.plist CFBundleShortVersionString
    Affected if Version number displayed is below 2.19.1
  3. Check application bundle contents
    Verify the app bundle exists at: /Applications/Yandex Telemost.app. Run: ls -la /Applications/ | grep -i telemost
    Affected if The application bundle exists and version cannot be determined or is below 2.19.1
  4. Verify installation location security
    Check the directory where Yandex Telemost is located. Run: ls -lae /Applications/Yandex\ Telemost.app/../ | head -20. Ensure the parent directory is not writable by untrusted users.
    Affected if Application is run from a directory with weak permissions such as Downloads folder, external drives, or shared network locations

User is affected if Yandex Telemost is installed with a version number lower than 2.19.1 on macOS, particularly if the application resides in a directory with untrusted write access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.19.1 or later
Fixed in 2.19.1
Interim mitigation

Upgrade Yandex Telemost to version 2.19.1 or later. Until upgraded, ensure the application runs from trusted directories and avoid running from locations with untrusted write access (e.g., downloaded folders, external drives).

Recommended fix High confidence

2.19.1 or later

  1. Check current installed version of Yandex Telemost by opening the application and navigating to About or checking in Applications folder
  2. Download the latest version of Yandex Telemost (version 2.19.1 or later) from the official Yandex website (yandex.com) or official download sources
  3. Uninstall the current version of Yandex Telemost from your Mac by dragging the application to Trash or using proper uninstallation method
  4. Install the newly downloaded Yandex Telemost 2.19.1 or later version by opening the installer package and following the installation prompts
  5. Verify the installed version by checking About Yandex Telemost to confirm version 2.19.1 or higher is now installed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Yandex Telemost Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5471 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5471 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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