CVE-2022-26086
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 PresentMon software maintained by Intel(R) before version 1.7.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 confidencePresentMon before version 1.7.1 contains an uncontrolled search path element vulnerability that allows an authenticated local user to perform DLL hijacking. A local attacker can place malicious DLLs in the application search path, which are then loaded with the application's privileges, potentially 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< 1.7.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.
-
Check if PresentMon is installedSearch for PresentMon.exe on the system using 'Get-ChildItem -Path C:\ -Recurse -Filter PresentMon.exe -ErrorAction SilentlyContinue' on Windows or 'find / -name PresentMon 2>/dev/null' on LinuxAffected if PresentMon.exe is found on the system
-
Identify the installed versionRun 'PresentMon.exe --version' or 'PresentMon.exe -version' from the installation directory to retrieve the version numberAffected if The command returns a version number less than 1.7.1
-
Verify the version is within affected rangeCompare the retrieved version against the affected range: any version below 1.7.1 is vulnerableAffected if Installed version is 1.7.0 or lower, or any pre-1.7.1 release
-
Check application directory permissionsInspect write permissions on the PresentMon installation directory. On Windows, right-click the folder, go to Properties > Security to see who has Write permission. On Linux, run 'ls -la /path/to/presentmon/'Affected if Non-privileged users have Write permission to the directory where PresentMon.exe resides, allowing them to place malicious DLLs
The system is affected if PresentMon is installed with a version lower than 1.7.1 and the installation directory permits non-privileged users to write files.
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 · scoped1.7.1
Upgrade PresentMon to version 1.7.1 or later to remediate this vulnerability. Additionally, ensure the application directory is protected and only writable by privileged users.
PresentMon version 1.7.1 or later
- Identify the currently installed version of PresentMon (check via the application's --version flag or installed location)
- Download PresentMon version 1.7.1 or later from the official Intel source (github.com/GameTechDev/PresentMon)
- Close any running PresentMon instances
- Upgrade/install the fixed version of PresentMon
- Verify the new version is installed and running (confirm version 1.7.1 or later is in use)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26086 — 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-26086 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