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

CVE-2025-20106

MEDIUM · 6.7 CVSS v3.1 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated

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 in some software installer for some VTune(TM) Profiler software and Intel(R) oneAPI Base Toolkits before version 2025.0. within Ring 3: User Applications may allow an escalation of privilege. System software adversary with an authenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires active user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

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

Uncontrolled search path vulnerability in Intel VTune Profiler and oneAPI Base Toolkit installers before version 2025.0. The installer searches for DLLs in an uncontrolled path, potentially allowing a locally authenticated attacker to place malicious DLLs that get loaded during installation, leading to privilege escalation.

MitigationUpgrade Intel VTune Profiler and oneAPI Base Toolkit to version 2025.0 or later to remediate this vulnerability.

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

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/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 Intel VTune Profiler is installed
    On Windows, open Programs and Features or check for 'Intel VTune Profiler' in the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\. On Linux, check /opt/intel/vtune or look for vtune in installed packages via 'dpkg -l | grep vtune' or 'rpm -qa | grep vtune'.
    Affected if Intel VTune Profiler is installed with a version lower than 2025.0
  2. Check if oneAPI Base Toolkit is installed
    On Windows, open Programs and Features or check for 'Intel oneAPI Base Toolkit' in the registry. On Linux, check /opt/intel/oneapi or look for oneapi-base-toolkit in installed packages.
    Affected if oneAPI Base Toolkit is installed with a version lower than 2025.0
  3. Determine installed version of Intel VTune Profiler
    On Windows, right-click the installed program in Programs and Features and select Properties, or check the uninstall registry entry for the Version value. On Linux, run 'vtune-backend --version' if available, or check the directory name under /opt/intel/vtune/ for a version number.
    Affected if Version displayed is below 2025.0 (for example, 2024.x, 2023.x, etc.)
  4. Determine installed version of oneAPI Base Toolkit
    On Windows, open Programs and Features, find Intel oneAPI Base Toolkit, and check the Version column. On Linux, check the installed package version or the directory /opt/intel/oneapi/ for version information.
    Affected if Version displayed is below 2025.0 (for example, 2024.x, 2023.x, etc.)

The environment is affected if either Intel VTune Profiler or oneAPI Base Toolkit is installed with a version prior to 2025.0, since the installer DLL search path vulnerability applies during the installation process of those versions.

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

Upgrade Intel VTune Profiler and oneAPI Base Toolkit to version 2025.0 or later to remediate this vulnerability.

Recommended fix High confidence

2025.0

  1. Identify the specific Intel software affected: VTune Profiler or Intel oneAPI Base Toolkit
  2. Check current installed version of the affected software
  3. Download Intel VTune Profiler version 2025.0 or later from official Intel sources
  4. Download Intel oneAPI Base Toolkit version 2025.0 or later from official Intel sources
  5. Uninstall the older vulnerable version following standard uninstall procedures
  6. Install the updated version 2025.0 or later
  7. Verify the installation completed successfully and the new version is running
  8. Confirm the DLL search path vulnerability is remediated by verifying no untrusted DLL locations are in the system PATH

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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