CVE-2022-26425
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 Collective Communications Library (oneCCL) before version 2021.6 for Intel(R) oneAPI Base 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 · moderate confidenceThis is an uncontrolled search path element vulnerability (DLL/library hijacking) in Intel oneAPI Collective Communications Library (oneCCL) before version 2021.6. The application uses an insecure library search path, allowing an authenticated local user to place malicious libraries in a location where oneCCL will load them during execution, potentially achieving 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< 2021.6CVSS 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 oneCCL installationSearch for the oneCCL installation directory - typically found under Intel oneAPI installation path (e.g., C:\Program Files (x86)\Intel\oneAPI\ or /opt/intel/oneapi/) and look for a 'ccl' or 'oneccl' folder. On Windows, also check for environment variable INTEL_ONEAPI_ROOT or OML_SDK_ROOT.Affected if oneCCL is not installed or the installation directory cannot be found, the system is likely not affected.
-
Determine installed oneCCL versionWithin the oneCCL installation directory, look for a version file, README, or check the DLL/properties. On Windows, right-click ccl.dll or similar library file and view Properties > Details for version info. On Linux, check the VERSION file or library symlinks in the ccl directory.Affected if The installed version is less than 2021.6, the system is affected by this vulnerability.
-
Examine library search path configurationCheck for environment variables that control library loading: PATH (Windows) or LD_LIBRARY_PATH (Linux). Also examine any configuration files or scripts that set these paths for oneCCL execution.Affected if The oneCCL library path includes directories writable by untrusted users (e.g., temp directories, user home directories, network shares), the vulnerability is exploitable.
-
Inspect for pre-existing malicious librariesIn the directories that appear in oneCCL's search path, look for unexpected DLL/SO files with suspicious names or recent modification dates, particularly in locations writable by non-admin users.Affected if Unexpected or recently modified libraries are found in the search path directories, this may indicate attempted exploitation.
The system is affected if Intel oneCCL is installed with a version prior to 2021.6 and the library search path includes directories writable by untrusted users, allowing potential DLL hijacking.
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 · scoped2021.6
Upgrade Intel oneCCL to version 2021.6 or later within the Intel oneAPI Base Toolkit. Ensure the upgraded library paths are secured and that no untrusted locations are added to the search path.
2021.6
- 1. Identify the currently installed version of Intel oneAPI Collective Communications Library (oneCCL) on the system
- 2. Download Intel oneCCL version 2021.6 or later from Intel's official website or package repository
- 3. Uninstall the vulnerable version of oneCCL (< 2021.6)
- 4. Install the fixed version (2021.6 or later) following Intel's installation instructions
- 5. Verify the installed version matches or exceeds 2021.6
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26425 — 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-26425 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