CVE-2022-26421
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 DPC++/C++ Compiler Runtime before version 2022.0 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 DPC++/C++ Compiler Runtime before version 2022.0 contains an uncontrolled search path element vulnerability. An authenticated local user can exploit this by placing malicious libraries or executables in a directory that the runtime searches, potentially leading to privilege escalation when the compiler runtime loads the crafted files.
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.0CVSS 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 oneAPI DPC++/C++ Compiler Runtime installationSearch the system for Intel oneAPI compiler runtime components. Check common installation directories or use system package management tools to list installed Intel oneAPI packages.Affected if The compiler runtime is present on the system
-
Determine installed runtime versionUse available system tools or examine the runtime binary version information to identify the exact version number of the installed DPC++/C++ Compiler Runtime.Affected if Version cannot be determined or is found to be below 2022.0
-
Compare version against affected rangeCompare the identified version against the affected range: versions earlier than 2022.0 are vulnerable.Affected if Installed version is earlier than 2022.0
The environment is affected if the Intel oneAPI DPC++/C++ Compiler Runtime is installed with a version earlier than 2022.0.
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.0
Upgrade the Intel oneAPI DPC++/C++ Compiler Runtime to version 2022.0 or later to remediate this vulnerability.
2022.0
- Check current version of Intel(R) oneAPI DPC++/C++ Compiler Runtime installed on the system
- Download Intel oneAPI DPC++/C++ Compiler Runtime version 2022.0 or later from the official Intel website or repository
- Uninstall the existing version of the oneAPI DPC++/C++ Compiler Runtime
- Install the downloaded version 2022.0 or later
- Verify the installation completed successfully and the version is correct
- Restart any running applications or services that may use the compiler runtime
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26421 — 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-26421 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