# CVE-2025-32086: Privilege escalation in Intel(R) Xeon(R) 6 Processors when using Intel(R) SGX or Intel(R) TDX

> A privileged local attacker can escalate privileges on Intel Xeon 6 processors using SGX or TDX due to improper security checks in DDRIO configuration.

- **Severity:** Medium 4.5 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Aug 2025
- **Updated:** 26 Feb 2026
- **Also known as:** ALPINE-CVE-2025-32086, BELL-CVE-2025-32086, DEBIAN-CVE-2025-32086, GHSA-4472-mrv9-mf4h, UBUNTU-CVE-2025-32086

## What is CVE-2025-32086?

CVE-2025-32086 is a medium-severity vulnerability in Intel(R) Xeon(R) 6 Processors when using Intel(R) SGX or Intel(R) TDX, published on 12 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improperly implemented security check for standard in the DDRIO configuration for some Intel(R) Xeon(R) 6 Processors when using Intel(R) SGX or Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.

Weakness: CWE-358 (Improperly Implemented Security Check for Standard)

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


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

Apply the vendor's patch.

## Is CVE-2025-32086 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32086 is a medium-severity vulnerability in Intel(R) Xeon(R) 6 Processors when using Intel(R) SGX or Intel(R) TDX, published on 12 Aug 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-32086 in the wild and no public exploit code.

Affected product: Intel(R) Xeon(R) 6 Processors when using Intel(R) SGX or Intel(R) TDX. 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-32086/ (Markdown: https://insights.sbomify.com/CVE-2025-32086/index.md)
```

## Sources

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

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