dbcve.org
Connectivity Performance SuiteApplication · Intel

CVE-2026-20772

MEDIUM · 6.7 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 50.25.1121.193 or later.
See remediation →
67/100
Remediation priority · Elevated

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 · unedited
Uncontrolled search path for some Intel(R) Connectivity Performance Suite software installers before version 50.25.1121.193 within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an authenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires active user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

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 confidence

Intel Connectivity Performance Suite installers before version 50.25.1121.193 contain an uncontrolled search path vulnerability (DLL hijacking) that allows an unprivileged authenticated user to cause the installer to load malicious DLLs from user-controllable locations, enabling local privilege escalation to higher privileges.

MitigationUpdate Intel Connectivity Performance Suite to version 50.25.1121.193 or later. Prior to deployment in production environments, test the updated installer to ensure it does not introduce compatibility issues with existing systems.

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
Connectivity Performance SuiteApplication
Affected:< 50.25.1121.193

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Intel Connectivity Performance Suite is installed
    Check for the presence of Intel Connectivity Performance Suite in the system. On Windows, look in Add/Remove Programs or check for the installation directory (typically under Program Files or Program Files (x86) with 'Intel' or 'Connectivity Performance Suite' in the name).
    Affected if The software is installed on the system
  2. Locate the installed version number
    Check the version of Intel Connectivity Performance Suite. In Windows, right-click the application in Add/Remove Programs and select Properties, or look for a version file in the installation directory. The version may also be visible in the program's About or Help section.
    Affected if Unable to determine the version number
  3. Compare installed version against the fixed version
    Compare your installed version to 50.25.1121.193. Versions before this (e.g., 50.x.x.x versions lower than 50.25.1121.193, or earlier version branches) are affected. Versions at or above 50.25.1121.193 are not affected.
    Affected if Installed version is earlier than 50.25.1121.193 (for example, 50.20.1000.50 or any version in the 1.x-49.x range)

If Intel Connectivity Performance Suite is installed and its version number is below 50.25.1121.193, the environment is affected by this DLL hijacking vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 50.25.1121.193 or later
Fixed in 50.25.1121.193
Interim mitigation

Update Intel Connectivity Performance Suite to version 50.25.1121.193 or later. Prior to deployment in production environments, test the updated installer to ensure it does not introduce compatibility issues with existing systems.

Recommended fix High confidence

50.25.1121.193

  1. 1. Identify the currently installed version of Intel(R) Connectivity Performance Suite via Add/Remove Programs or the application's About/Help section
  2. 2. Navigate to the official Intel support website or Intel.com to locate the download page for Intel Connectivity Performance Suite
  3. 3. Download version 50.25.1121.193 or any later available version
  4. 4. Uninstall the current (vulnerable) version of Intel Connectivity Performance Suite through Windows Control Panel > Programs and Features
  5. 5. Install the newly downloaded patched version (50.25.1121.193 or later)
  6. 6. Restart the system if prompted by the installer
  7. 7. Verify the installed version matches the patched release (50.25.1121.193 or later)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Connectivity Performance Suite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20772 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-20772 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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