dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2025-31647

MEDIUM · 6.7 CVSS v3.1 Published 2025-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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) Graphics Software before version 25.22.1502.2 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 Graphics Software before version 25.22.1502.2 contains an uncontrolled search path vulnerability (DLL preloading) in Ring 3 user applications. A local, authenticated attacker with high complexity and active user interaction can exploit this to escalate privileges by tricking the software into loading malicious DLLs from an uncontrolled path.

MitigationUpgrade Intel Graphics Software to version 25.22.1502.2 or later. Until then, ensure only trusted executables run and monitor for suspicious DLL loading activity.

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 checks

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

  1. Locate Intel Graphics Software installation
    Check Windows Registry at HKLM\SOFTWARE\Intel\IGFX or view installed programs in Programs and Features for Intel Graphics Control Panel or Intel Graphics Driver
    Affected if Intel Graphics Software is present on the system
  2. Determine installed version
    Open Intel Graphics Control Panel and navigate to Information, or read registry value at HKLM\SOFTWARE\Intel\IGFX\Version. Compare the version string to 25.22.1502.2
    Affected if Version is present and is lower than 25.22.1502.2
  3. Identify vulnerable user-mode executables
    Check for Intel graphics Ring 3 applications in Program Files\Intel\Intel Graphics\ or C:\Windows\System32\DriverStore\FileRepository\ for executables such as igfxEML.exe, igfxHK.exe, or GraphicsDriverInstaller.exe
    Affected if These Intel graphics user-mode executables exist and can be launched by a user
  4. Verify DLL loading behavior
    Attempt to launch any Intel graphics user-mode application and monitor DLL loading with Process Monitor, observing if DLLs are loaded from the application working directory without full path specification
    Affected if The applications load DLLs from the current working directory rather than using secure absolute paths

The system is affected if Intel Graphics Software is installed with a version lower than 25.22.1502.2 and Intel graphics Ring 3 user-mode applications are present and executable.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Intel Graphics Software to version 25.22.1502.2 or later. Until then, ensure only trusted executables run and monitor for suspicious DLL loading activity.

Recommended fix Moderate confidence

Intel Graphics Software version 25.22.1502.2 or later

  1. Identify your Intel Graphics hardware by opening Device Manager and expanding 'Display adapters'
  2. Visit the official Intel Driver & Support page (intel.com/support) or use Intel Driver & Support Assistant
  3. Enter your system model or allow automatic detection of Intel Graphics components
  4. Download Intel Graphics Software version 25.22.1502.2 or later
  5. Run the installer as Administrator and follow the on-screen prompts
  6. Restart the system after installation completes
  7. Verify the installed version matches or exceeds 25.22.1502.2 via Device Manager or Intel Graphics Control Panel
Caveat Intel driver updates are generally safe; however, ensure backup of current settings and verify compatibility with specific GPU model before deployment in enterprise environments

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31647 — 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-2025-31647 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