CVE-2023-41091 is a medium severity uncontrolled search path flaw in Intel MPI Library before version 2021.11. NVD scores it 6.7. An authenticated local user may be able to escalate privileges. Upgrade to 2021.11 or later, and read Intel's advisory SA-01005 for the details.
What's affected
The record says the flaw affects some Intel MPI Library software before version 2021.11, so 2021.11 is the first fixed version named. The weakness is CWE-427, uncontrolled search path element.
The vector is local, high attack complexity, low privileges, with user interaction required, and high impact on confidentiality, integrity and availability. That adds up to 6.7. The record describes the attacker as an authenticated user with local access.
The record cites one reference: Intel security advisory INTEL-SA-01005. When this post was prepared, Intel's site refused my request, so I could not read the advisory. The description above and the fixed version come from the NVD record alone. Open the advisory to confirm which components are affected and what Intel recommends.
The CVE is not in CISA's KEV catalog. The record does not say it is exploited in the wild.
How to check if you're exposed
Find out where Intel MPI is installed and which version it is. On Linux, with the library on your path:
mpirun --version
mpiexec --version
If you use the oneAPI toolkit, the install directory normally holds a folder per version, which you can list:
ls /opt/intel/oneapi/mpi
Look in shared HPC images, container images and build environments too, since MPI often ships baked into them. Any version below 2021.11 is in scope.
Then look at who can log in to those hosts. The attacker needs local access, so the exposure is largest on shared clusters and multi-user workstations, where many accounts run code on the same machine.
What to do now
- Inventory the hosts, images and containers that include Intel MPI Library and record each version.
- Upgrade to version 2021.11 or later, and test your MPI jobs on a staging node before you roll it out to the cluster.
- Read Intel's advisory SA-01005 to confirm the affected components and any extra steps.
- Check that directories on your library and executable search paths are writable only by trusted administrators.
- Rebuild shared images so new nodes do not come up with the old version.
Why it matters
An uncontrolled search path means a program looks for a file or library in places that an attacker may be able to write to. If a privileged process loads the attacker's file instead of the real one, the attacker's code runs with that process's authority. This is why the record treats it as privilege escalation.
The score is medium because exploitation needs a local account, high complexity and user interaction. On shared research clusters the local account condition is easy to meet, since users are expected to run their own code. The fix is a routine upgrade, and good housekeeping of search paths limits this whole class of bug.
Quick check
Is this exploitable over the network?
No. The record lists a local attack vector and an authenticated user.
Which version fixes it?
The record says versions before 2021.11 are affected. Confirm in Intel's advisory SA-01005.
Sources
- Intel security advisory INTEL-SA-01005 (access was denied when fetched, so details come from the NVD record)
- Safeguard Gold entry for CVE-2023-41091
Last reviewed: 19 October 2026.
