CVE-2025-20627
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 for some Intel(R) oneAPI DPC++/C++ Compiler software before version 2025.0.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 DPC++/C++ Compiler before version 2025.0.1 contains an uncontrolled search path vulnerability where the application loads libraries or resources from locations that can be influenced by an authenticated local user, potentially allowing privilege escalation to a higher privileged context.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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.
-
Verify Intel oneAPI DPC++/C++ Compiler is installedCheck for the presence of the Intel compiler installation directory (commonly under C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\) or use system inventory tools to list installed software containing 'Intel oneAPI' or 'DPC++' in the nameAffected if The compiler is installed on the system
-
Determine installed compiler versionLocate the compiler executable (such as icx.exe or dpcpp.exe) and run it with a version flag, for example: 'icx --version' or 'dpcpp --version' from the Intel compiler bin directoryAffected if The version returned is earlier than 2025.0.1 (for example, 2024.x, 2023.x, or earlier)
-
Compare version against the fixed releaseParse the version number output from the previous step and compare it numerically or lexicographically to 2025.0.1Affected if The installed version is less than 2025.0.1
-
Examine library search paths used by the compilerReview the PATH environment variable and any compiler-specific environment variables (such as CPATH, LIB, or Intel-specific variables) to identify directories that may be writable by non-privileged usersAffected if The search paths include user-writable directories that could be manipulated to supply malicious libraries
The system is affected if the Intel oneAPI DPC++/C++ Compiler is installed with a version earlier than 2025.0.1 and the compiler's library search paths include locations writable by lower-privileged 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 · scopedUpdate Intel oneAPI DPC++/C++ Compiler to version 2025.0.1 or later to obtain the vendor fix for this vulnerability.
2025.0.1
- Identify the current version of Intel(R) oneAPI DPC++/C++ Compiler installed on the system
- Navigate to the official Intel download page or repository to obtain version 2025.0.1 or later
- Uninstall the current (vulnerable) version of the Intel oneAPI DPC++/C++ Compiler
- Install the fixed version 2025.0.1 of the Intel oneAPI DPC++/C++ Compiler
- Verify the installed version matches 2025.0.1 or later using the compiler version flag or Intel oneAPI utility
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20627 — 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-2025-20627 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