Safeguard
Vulnerability Analysis•

CVE-2023-32647: Medium Access Control Flaw in Intel XTU

CVE-2023-32647 is a medium severity improper access control in Intel Extreme Tuning Utility before 7.12.0.29. Update XTU to 7.12.0.29 or later.

Safeguard Security Team
3 min read

CVE-2023-32647 is a medium severity (CVSS 6.8) improper access control flaw in Intel Extreme Tuning Utility (XTU) before version 7.12.0.29. An authenticated local user may escalate privileges. Intel recommends updating XTU to version 7.12.0.29 or later, available from its download page.

What's affected

Intel advisory INTEL-SA-00955 lists Intel XTU versions before 7.12.0.29 as affected, and 7.12.0.29 as the fixed version. Intel provides downloads on its site.

The weakness is CWE-284, improper access control. XTU is a tool for tuning and monitoring processor performance. Tools of this kind work close to system functions, so access control inside them matters.

The vector is local, low complexity, low privileges and user interaction required, with low confidentiality impact and high integrity and availability impact. The record and Intel agree on the medium rating and the 6.8 score.

How to check if you're exposed

Open Intel XTU and read the version in the About page, or look in Installed apps for Intel Extreme Tuning Utility. In PowerShell:

Get-Package -Name "Intel*Extreme Tuning*"

If the version is below 7.12.0.29, update it.

What to do now

  1. Find PCs with Intel XTU installed, including performance workstations.
  2. Update to 7.12.0.29 or later from Intel.
  3. Remove XTU from machines that do not need it.
  4. Restrict who can install tuning tools on managed devices.
  5. Confirm the version after the update.

Why it matters

Tuning tools reach deep into system settings, so they run components with high rights. If the access controls on those components are too loose, a standard user can ask the privileged part to do things on their behalf. That is the class this CVE belongs to.

The need for local access and user interaction keeps the risk modest for most fleets. It is more relevant on shared workstations. The record does not report exploitation and the KEV flag is false.

Removing software you do not need is the cheapest fix of all. Pair that habit with the free in-browser dependency scan for your own code.

If you run XTU on workstations, also ask users why they need it. Overclocking and tuning tools tend to spread by word of mouth, and removing an unused copy removes the risk entirely.

If you manage a fleet, treat tuning utilities as optional software. Many machines carry XTU because someone tried it once. A quick search of your device management console for the product name shows how many copies exist and which versions they run.

Quick check

Which version fixes CVE-2023-32647?

Intel XTU 7.12.0.29 or later, per INTEL-SA-00955.

Is a remote attack possible?

No. The record lists a local attack vector.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.