dbcve.org
Mpi LibraryApplication · Intel

CVE-2022-26052

HIGH · 7.3 CVSS v3.1 Published 2023-02-16
Fix available
A fix is available. Upgrade to 2021.6 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) MPI Library before version 2021.6 for Intel(R) oneAPI HPC Toolkit 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 · high confidence

This is an uncontrolled search path element vulnerability in Intel MPI Library versions prior to 2021.6. The vulnerability allows an authenticated local user to potentially escalate privileges by manipulating the library search path, likely through DLL/dynamic library hijacking orbinPath manipulation techniques.

MitigationUpdate Intel(R) MPI Library to version 2021.6 or later. Prior to deployment, inventory all systems running the affected library version, test the update in a non-production environment to verify MPI functionality, and schedule maintenance windows for production systems.

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
Mpi LibraryApplication
Affected:< 2021.6

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. Check if Intel MPI Library is installed
    Search for the Intel MPI Library installation directory in common locations: C:\Program Files\Intel\, C:\Program Files (x86)\Intel\, or check registry key HKLM\SOFTWARE\Intel\MPI or HKLM\SOFTWARE\WOW6432Node\Intel\MPI for the InstallDir value.
    Affected if Intel MPI Library is found on the system
  2. Identify the installed version of Intel MPI Library
    Locate the mpi.dll file or the Intel MPI Library version info in the installation directory. Right-click on the file, select Properties, and check the Version tab. Alternatively, run 'mpirun --version' if available in PATH.
    Affected if The version displayed is any version prior to 2021.6 (e.g., 2021.5, 2021.4, 2019.x, etc.)
  3. Verify the library search path configuration
    Check environment variables for MPI-related paths: %I_MPI_ROOT%, %PATH%, and %LIB%. Also examine any mpivars.bat or configuration scripts in the Intel MPI installation directory for hardcoded or relative paths.
    Affected if The library uses relative or writable paths in its search configuration that could be manipulated
  4. Check for running MPI processes or services
    Use Task Manager or command 'tasklist | findstr mpi' to see if mpirun.exe, mpispawn.exe, or related Intel MPI processes are currently active. Check if MPI jobs are scheduled or commonly run.
    Affected if Intel MPI processes are actively running or scheduled to run on the system
  5. Confirm user context and permissions
    Review which local users have access to the Intel MPI installation directory and its subdirectories. Check folder permissions to see if standard users can write to directories within the MPI library path.
    Affected if Authenticated local users have write permissions to any directory in the MPI library search path

The system is affected if Intel MPI Library version prior to 2021.6 is installed and the library search path contains writable locations accessible to local authenticated 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 2021.6 or later
Fixed in 2021.6
Interim mitigation

Update Intel(R) MPI Library to version 2021.6 or later. Prior to deployment, inventory all systems running the affected library version, test the update in a non-production environment to verify MPI functionality, and schedule maintenance windows for production systems.

Recommended fix High confidence

2021.6

  1. Navigate to the Intel website and download Intel(R) MPI Library version 2021.6 or later
  2. Install the updated Intel MPI Library following Intel's standard installation procedures
  3. Verify the installed version is 2021.6 or later by checking the library version

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

Fix this in Mpi Library Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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