CVE-2023-32618 is a medium severity (CVSS 6.7) uncontrolled search path flaw in some Intel oneAPI Toolkit and component software installers before version 4.3.2. An authenticated local user may escalate privileges. Intel recommends updating the toolkits to 2023.2.0 or later and standalone components to their latest versions.
What's affected
Intel advisory INTEL-SA-00956 covers the installers of many oneAPI products. The record names installers before version 4.3.2. Intel's table lists the fixed release for each product, for example:
- oneAPI Base Toolkit, HPC Toolkit, IoT Toolkit and Rendering Toolkit: 2023.2.0
- oneAPI DPC++/C++ Compiler: 2023.2.0
- Intel Fortran Compiler: 2023.2.1
- oneAPI Math Kernel Library: 2023.2.0
- Intel MPI Library: 2021.10.0
- oneAPI Threading Building Blocks: 2021.10.0
- Intel Integrated Performance Primitives: 2021.9.0
- Intel IPP Cryptography: 2021.8.0
- oneAPI DPC++ Library (oneDPL): 2022.2.0
The advisory lists more than two dozen products. Use Intel's table for the exact version of the component you installed.
The weakness is CWE-427, uncontrolled search path element. Intel and the record agree on the medium rating and the 6.7 score.
How to check if you're exposed
Read the installed oneAPI versions on each workstation or build server. On Linux, the default install location holds the version folders:
ls /opt/intel/oneapi
On Windows, open Installed apps and look for entries beginning with Intel oneAPI. Compare each version with the fixed release in Intel's table. Anything below its fixed version needs an update.
What to do now
- Find machines with oneAPI toolkits or components, including build servers and CI images.
- Update toolkits to 2023.2.0 or later. Update standalone components to their latest versions.
- Rebuild container and virtual machine images that bake in an old installer.
- Run installers only from folders that ordinary users cannot write to.
- Record the toolkit versions in your build documentation.
Why it matters
An uncontrolled search path means the installer looks for a file, such as a library, in places an attacker might control, and it trusts what it finds first. A local user who can drop a file in such a location can have their code run with the installer's rights.
The vector needs a local, authenticated user, high attack complexity and user interaction. That reduces the practical risk to shared build servers and developer workstations. The record does not report exploitation and the KEV flag is false.
Developer toolchains are part of the software supply chain. Use the free in-browser dependency scan on your projects and the Gold directory for vendor advisories, and add toolchain versions to your inventory.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Which versions fix CVE-2023-32618?
Intel lists 2023.2.0 for most toolkits, with product specific releases for others. See INTEL-SA-00956.
Who is at risk?
Mainly shared machines where a local user could place files that the installer will find.
Sources
Last reviewed: 19 October 2026.