CVE-2022-26345
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 · uneditedUncontrolled search path element in the Intel(R) oneAPI Toolkit OpenMP before version 2022.1 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 confidenceThe Intel oneAPI Toolkit OpenMP runtime uses an uncontrolled search path when loading libraries, allowing an authenticated local user to place a malicious DLL in the search path and achieve privilege escalation.
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< 2022.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate Intel OpenMP runtime librarySearch for libiomp5.dll (Windows) or libiomp5.so (Linux) in common Intel oneAPI installation directories such as C:\Program Files\Intel\oneAPI\ or C:\Program Files (x86)\Intel\oneAPI\, or check your system PATH environment variable for Intel oneAPI paths.Affected if The library file exists in an Intel oneAPI directory on the system.
-
Identify the exact file versionRight-click the libiomp5.dll file, select Properties, then view the Details tab to see the File Version. Alternatively, use a command like 'dir /a C:\Program Files*\Intel\oneAPI\*libiomp5*' on Windows or 'find /opt /usr -name "libiomp5*" 2>/dev/null' on Linux.Affected if A version number is displayed in the file properties.
-
Compare installed version to affected rangeCompare the discovered file version against version 2022.1. Note that versions below 2022.1 are affected (for example, 2021.x versions would be vulnerable).Affected if The installed version is lower than 2022.1 (for example, 2021.1, 2021.2, etc.).
The system is affected if Intel OpenMP runtime library (libiomp5) is installed with a version lower than 2022.1.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2022.1
Update Intel oneAPI Toolkit OpenMP to version 2022.1 or later to remediate this vulnerability.
2022.1 or later
- Verify the current version of Intel oneAPI Toolkit OpenMP installed on the system
- Download Intel oneAPI Toolkit version 2022.1 or later from the official Intel website or appropriate distribution channel
- Install the updated version following Intel's standard installation procedures
- Verify the installation completed successfully and the version is now 2022.1 or later
- Confirm the DLL search path vulnerability is remediated by ensuring OpenMP binaries are loaded from controlled, secure locations only
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-26345 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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