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

CVE-2025-12046

HIGH · 7.8 CVSS v3.1 Published 2025-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A DLL hijacking vulnerability was reported in the Lenovo App Store and Lenovo Browser applications that could allow a local authenticated user to execute code with elevated privileges under certain conditions.

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 confidence

This is a DLL hijacking vulnerability in Lenovo App Store and Lenovo Browser applications where a local authenticated user can place a malicious DLL in a location that the vulnerable application loads from, achieving code execution with elevated privileges.

MitigationApply vendor patches from Lenovo when available. Until then, restrict write access to application directories and monitor for suspicious DLL files in those locations.

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
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. Identify installed Lenovo applications
    Check for Lenovo App Store and Lenovo Browser installations. On Windows, inspect common installation paths such as C:\Program Files\Lenovo\App Store or C:\Program Files\Lenovo\LenovoBrowser. Use PowerShell command: Get-ChildItem 'C:\Program Files\Lenovo' -ErrorAction SilentlyContinue | Select-Object Name
    Affected if Lenovo App Store or Lenovo Browser is installed on the system
  2. Locate application executable directories
    Find the installation directories of Lenovo App Store and Lenovo Browser. Typical locations include C:\Program Files\Lenovo\App Store\ and C:\Program Files\Lenovo\LenovoBrowser\. Right-click the shortcuts for these applications and select 'Open file location' to confirm paths
    Affected if The application binaries are located in directories with weak permissions
  3. Enumerate DLL files in application directories
    List all DLL files in the Lenovo App Store and Lenovo Browser installation directories. Use command: Get-ChildItem 'C:\Program Files\Lenovo\App Store\' -Filter *.dll -Recurse -ErrorAction SilentlyContinue | Select-Object FullName, LastWriteTime
    Affected if Unexpected or recently modified DLL files are present that were not shipped with the application
  4. Check write permissions on application directories
    Review ACL permissions on the Lenovo App Store and Lenovo Browser directories. Use icacls command: icacls 'C:\Program Files\Lenovo\App Store' or check via Security tab in folder Properties. Verify that standard users do not have Write or Modify permissions to these directories
    Affected if Non-administrative users have Write or Modify access to application directories, allowing DLL injection
  5. Monitor for DLL search order hijacking opportunities
    Identify if application directories are present in system PATH or are loaded before system directories. Check application manifest or use Process Monitor (Sysinternals) to observe DLL load behavior when launching the applications
    Affected if The vulnerable application loads DLLs from directories with weak permissions before system directories

A user is affected if Lenovo App Store or Lenovo Browser is installed and the application directories allow standard users to write files, enabling DLL hijacking injection.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches from Lenovo when available. Until then, restrict write access to application directories and monitor for suspicious DLL files in those locations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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