# CVE-2025-20010: Supply chain in Intel(R) Processor Identification Utility

> An authenticated local attacker can escalate privileges by exploiting unmaintained third-party components in the Intel Processor Identification Utility.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-j2mf-x92x-cpm8

## What is CVE-2025-20010?

CVE-2025-20010 is a high-severity vulnerability in Intel(R) Processor Identification Utility, published on 11 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Use of unmaintained third party components for some 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 low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no 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.

Weakness: CWE-1104 (Use of Unmaintained Third Party Components)

## Which versions are affected by CVE-2025-20010?


## How do I fix CVE-2025-20010?

No fix has been published for CVE-2025-20010 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-20010 being exploited?

There is no known exploitation of CVE-2025-20010 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-20010 and fix it if it is affected.

What it is: CVE-2025-20010 is a high-severity vulnerability in Intel(R) Processor Identification Utility, published on 11 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-20010 in the wild and no public exploit code.

Affected product: Intel(R) Processor Identification Utility. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-20010/ (Markdown: https://insights.sbomify.com/CVE-2025-20010/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-20010
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-20010
- OSV: https://osv.dev/vulnerability/CVE-2025-20010

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-20010/
Summaries are generated and may contain mistakes; the official description above is the record.