dbcve.org
Distribution For PythonApplication · Intel

CVE-2022-26032

HIGH · 7.3 CVSS v3.1 Published 2023-02-16
Fix available
A fix is available. Upgrade to 2022.1 or later.
See remediation →
73/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 element in the Intel(R) Distribution for Python programming language before version 2022.1 for Intel(R) oneAPI Toolkits may allow an authenticated user to potentially enable escalation of privilege via local access.

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 an uncontrolled search path element vulnerability in Intel Distribution for Python before version 2022.1. The application uses a search path to locate libraries or modules without properly restricting or validating that path, allowing an authenticated local user to potentially place malicious code in a location the application will search and execute, leading to privilege escalation.

MitigationUpgrade to Intel Distribution for Python version 2022.1 or later. Additionally, review and restrict the Python search path (PYTHONPATH, site-packages locations) and ensure untrusted users cannot write to directories in the search path.

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
Distribution For PythonApplication
Affected:< 2022.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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. Identify Intel Distribution for Python installation
    Run 'where idp' on Windows or 'which idp' on Linux to locate the Intel Distribution for Python executable, or check for 'intel' in the installed Python packages via 'pip list' looking for intel-related packages.
    Affected if Intel Distribution for Python is installed on the system
  2. Determine installed version
    Run the Intel Python interpreter with '--version' or use 'idp --version' to retrieve the exact version number, or inspect the installation metadata.
    Affected if The displayed version is lower than 2022.1 (e.g., 2021.x, 2020.x, or earlier)
  3. Verify Python search path configuration
    Execute 'python -c "import sys; print(sys.path)"' or 'idp -c "import sys; print(sys.path)"' to list all directories Python searches for modules.
    Affected if Directories in the search path are writable by untrusted users or contain unsanitized user-controlled paths (PYTHONPATH environment variable)
  4. Check for untrusted writable directories in search path
    Review the sys.path output and verify file system permissions on each directory to identify any locations writable by low-privilege or untrusted users.
    Affected if Any directory in the Python search path allows write access to authenticated local users who could place malicious code

The environment is affected if Intel Distribution for Python version less than 2022.1 is installed AND the Python search path contains directories writable by untrusted users.

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 2022.1 or later
Fixed in 2022.1
Interim mitigation

Upgrade to Intel Distribution for Python version 2022.1 or later. Additionally, review and restrict the Python search path (PYTHONPATH, site-packages locations) and ensure untrusted users cannot write to directories in the search path.

Recommended fix High confidence

2022.1

  1. 1. Check the currently installed version of Intel Distribution for Python (e.g., using 'conda list' or checking the installation directory)
  2. 2. Download Intel Distribution for Python version 2022.1 or later from the official Intel website or Intel oneAPI toolkit downloads
  3. 3. Uninstall the current version following standard uninstallation procedures
  4. 4. Install the downloaded version 2022.1 or later using the Intel installer
  5. 5. Verify the installation completed successfully and confirm the new version is installed
Caveat Review Intel release notes for version 2022.1 to check for any functionality changes or migration requirements

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

Fix this in Distribution For Python Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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