CVE-2022-26512
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) FPGA Add-on for Intel(R) oneAPI Base Toolkit before version 2022.2 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 FPGA Add-on for Intel oneAPI Base Toolkit before version 2022.2 contains an uncontrolled search path element vulnerability. This allows an authenticated local attacker to potentially hijack executable or library loading by placing malicious files in directories searched by the application before legitimate locations, leading to 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.2CVSS 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.
-
Confirm Intel FPGA Add-on installationCheck if Intel FPGA Add-on for Intel oneAPI Base Toolkit is installed on the system. This may be found in Program Files/Intel, or use system inventory tools to list installed Intel software packages.Affected if The product is not installed or not present on the system
-
Identify installed versionLocate the installed version of Intel FPGA Add-on for Intel oneAPI Base Toolkit. Check the software listing in Add/Remove Programs, or look for version information in the Intel installation directory.Affected if The version cannot be determined or the product is not found
-
Compare version to affected rangeCompare the identified version against the affected range: any version prior to 2022.2 is vulnerable. Versions 2022.2 and later are not affected.Affected if The installed version is earlier than 2022.2 (for example, 2022.1, 2021.x, or earlier)
-
Review executable search pathsIf the vulnerable version is installed, examine the application's search paths for executable and library loading. Check environment variables and application configuration for paths that may be writable by lower-privilege users.Affected if The application loads executables or libraries from user-writable directories before secure locations
The environment is affected if Intel FPGA Add-on for Intel oneAPI Base Toolkit version earlier than 2022.2 is installed and the application searches paths controllable by local users.
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.2
Update to Intel FPGA Add-on for Intel oneAPI Base Toolkit version 2022.2 or later which contains the fix for this vulnerability.
2022.2
- 1. Identify the current installed version of Intel(R) FPGA Add-on for Intel(R) oneAPI Base Toolkit via the Intel Quartus Prime or oneAPI installation tools
- 2. Navigate to the official Intel website and download version 2022.2 or later of the Intel FPGA Add-on for Intel oneAPI Base Toolkit
- 3. Uninstall the current version following Intel's documented uninstallation procedures
- 4. Install the downloaded version 2022.2 or later using the Intel installation wizard
- 5. Verify the installation completed successfully and confirm the version number matches 2022.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26512 — 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-26512 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