dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2025-5470

HIGH · 7.3 CVSS v4.0 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/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 Disk on MacOS allows Search Order Hijacking.This issue affects Disk: before 3.2.45.3275.

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 Disk for MacOS before version 3.2.45.3275 contains an Uncontrolled Search Path Element vulnerability that allows Search Order Hijacking. The application uses an insecure search path to locate dynamic libraries, enabling an attacker to place a malicious library in a location that gets searched before the legitimate one, leading to arbitrary code execution with the privileges of the Yandex Disk process.

MitigationUpdate Yandex Disk to version 3.2.45.3275 or later to remediate this vulnerability. Until then, ensure only trusted files are present in directories that Yandex Disk searches for libraries.

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:Amber

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. Verify Yandex Disk is installed
    Check if Yandex Disk.app exists in /Applications folder, or search via Spotlight for 'Yandex Disk'. Also check for running process with command: ps aux | grep -i 'Yandex Disk'
    Affected if Yandex Disk application is present on the system
  2. Determine installed version
    Right-click Yandex Disk.app in /Applications, select 'Get Info', and read the Version field. Alternatively, run: defaults read /Applications/Yandex\ Disk.app/Contents/Info CFBundleShortVersionString
    Affected if Version number is lower than 3.2.45.3275, or version cannot be determined (application is still considered vulnerable if unpatched)
  3. Inspect application library load paths
    Use command: otool -L /Applications/Yandex\ Disk.app/Contents/MacOS/Yandex\ Disk | head -20. This shows all dynamic libraries the application loads and their search order
    Affected if Output shows loading of .dylib files from user-writable directories such as current working directory, ~/Library/Frameworks, or paths containing '.' (current directory) before system library paths
  4. Check for suspicious dylib files in common hijack locations
    Search for unexpected .dylib files in locations that may be searched: find /Applications/Yandex\ Disk.app -name '*.dylib' -type f 2>/dev/null; ls -la ~/Library/Frameworks/ 2>/dev/null; ls -la ./ | grep -i '.dylib' (in directories where Yandex Disk may run)
    Affected if Unexpected or unsigned .dylib files exist in the application's directory tree or in user-writable framework directories that precede system library paths in the search order

You are affected if Yandex Disk is installed and the installed version is lower than 3.2.45.3275, AND the application loads dylib files from user-writable or untrusted directories in its library search path.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Yandex Disk to version 3.2.45.3275 or later to remediate this vulnerability. Until then, ensure only trusted files are present in directories that Yandex Disk searches for libraries.

Recommended fix High confidence

Yandex Disk 3.2.45.3275 or later

  1. Open Yandex Disk on your Mac
  2. Click on the Yandex Disk menu in the top-left corner of the screen
  3. Select 'About Yandex Disk' from the dropdown menu
  4. Check if your current version is below 3.2.45.3275
  5. If the version is before 3.2.45.3275, open a web browser and go to the official Yandex Disk download page: https://disk.yandex.com/download
  6. Download the latest version of Yandex Disk for macOS
  7. Open the downloaded .dmg file
  8. Drag the Yandex Disk app to your Applications folder to install the update

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5470 — 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-5470 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