dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-27246

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
Incorrect default permissions for the Intel(R) Processor Identification Utility before version 8.0.43 within Ring 3: User Applications may allow an escalation of privilege. System software adversary with an authenticated user combined with a high complexity attack may enable local code execution. 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 · moderate confidence

The Intel Processor Identification Utility before version 8.0.43 contains incorrect default file permissions within its installation directory that could allow an authenticated local user to modify executable files or configurations, potentially leading to local privilege escalation. The vulnerability requires high-complexity attack with active user interaction.

MitigationUpdate Intel Processor Identification Utility to version 8.0.43 or later to obtain corrected default permissions. Alternatively, manually restrict permissions on the utility's installation directory to prevent modification by standard users.

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. Verify Intel Processor Identification Utility is installed
    Check for the application in Program Files (typically C:\Program Files\Intel\Processor Identification Utility or C:\Program Files (x86)\Intel\Processor Identification Utility) or look for the executable file (ProcessorID.exe or similar)
    Affected if The application is found in the system
  2. Determine the installed version
    Right-click the executable, select Properties, and check the Details tab for Product Version. Alternatively, run the utility and check Help > About
    Affected if Version is below 8.0.43 or version cannot be determined (may indicate unpatched older install)
  3. Locate the installation directory
    Right-click the executable shortcut or exe file, select Open file location to find the installation folder path
    Affected if A specific installation directory exists (default permissions apply to this location)
  4. Check write permissions for standard users
    Right-click the installation folder, select Properties > Security tab. Check permissions for Users or Standard Users group. Look for Write and Modify permissions under Allow
    Affected if Standard user accounts (non-administrators) have Write, Modify, or Full Control permissions to the installation directory or its executables
  5. Verify executable file permissions
    Within the installation folder, check individual .exe files (such as ProcessorID.exe) for permissions. Right-click > Properties > Security and verify if Users group has Modify or Write access
    Affected if Executable files are modifiable by non-administrator users

A user is affected if the installed version is below 8.0.43 AND standard (non-admin) user accounts have Write or Modify permissions on the utility's installation directory or its executable files, allowing potential local privilege escalation.

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

Update Intel Processor Identification Utility to version 8.0.43 or later to obtain corrected default permissions. Alternatively, manually restrict permissions on the utility's installation directory to prevent modification by standard users.

Recommended fix High confidence

Intel Processor Identification Utility version 8.0.43 or later

  1. Navigate to the official Intel website and locate the Intel Processor Identification Utility download page
  2. Download version 8.0.43 or later of the Intel Processor Identification Utility
  3. Close any running instances of the Intel Processor Identification Utility
  4. Run the installer with administrator privileges
  5. Follow the on-screen prompts to complete the installation
  6. Verify the installed version matches or exceeds 8.0.43

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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-2025-27246 — 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-27246 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