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

CVE-2025-30182

MEDIUM · 6.7 CVSS v3.1 Published 2025-11-11
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 for some Intel(R) Distribution for Python software installers before version 2025.2.0 within Ring 3: User Applications may allow an escalation of privilege. Unprivileged 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

Intel Distribution for Python installers before version 2025.2.0 contain an uncontrolled search path vulnerability (DLL search order hijacking) in Ring 3 user applications. An authenticated, unprivileged user with local access could exploit this high-complexity attack requiring active user interaction to achieve privilege escalation by causing the installer to load malicious DLLs from an attacker-controlled location.

MitigationUpgrade Intel Distribution for Python to version 2025.2.0 or later to eliminate the uncontrolled search path. Verify no vulnerable versions remain in the environment.

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. Locate Intel Distribution for Python installation
    Search for the product in standard installation directories (e.g., C:\Program Files\Intel\ on Windows, /opt/intel/ or ~/intel/ on Linux). Check Windows Registry under HKLM\SOFTWARE\Intel\Python or HKCU\SOFTWARE\Intel\Python for install paths.
    Affected if Intel Distribution for Python is found in the environment.
  2. Identify the installed version
    Examine version metadata in the installation directory or installer executable. On Windows, right-click the installer .exe and select Properties > Details to view File Version. On Linux, check the installer script or package metadata.
    Affected if The version is before 2025.2.0.
  3. Check for vulnerable installer binaries
    Look for installer executable files (setup.exe, install.py, or similar) in the installation directory or in downloaded installer packages. Note that the vulnerability affects the installer process itself, not the installed Python runtime.
    Affected if Installer binaries exist with version information indicating a version earlier than 2025.2.0.
  4. Verify installation method
    Determine whether the product was installed using a standalone installer (versus package manager or conda). The DLL hijacking occurs during installer execution, so note if manual installer runs are possible.
    Affected if Standalone installer executables are present and could be re-run by a local user.

A user is affected if Intel Distribution for Python (or its installer) version is detected and the version is earlier than 2025.2.0.

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 Distribution for Python to version 2025.2.0 or later to eliminate the uncontrolled search path. Verify no vulnerable versions remain in the environment.

Recommended fix Moderate confidence

2025.2.0

  1. Verify current installed version of Intel Distribution for Python by checking the installation directory or using package management tools
  2. Download Intel Distribution for Python version 2025.2.0 or later from the official Intel website or trusted Intel distribution channels
  3. Backup any existing Python projects, virtual environments, and custom configurations before upgrading
  4. Uninstall the current version of Intel Distribution for Python through the system's program removal mechanism
  5. Install the updated version (2025.2.0 or later) using the downloaded installer
  6. Verify the installation completed successfully and the new version is active
  7. Test critical Python workflows to ensure compatibility with the updated distribution
Caveat Review release notes for Intel Distribution for Python 2025.2.0 for any API or dependency changes that may affect existing Python code or workflows

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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