# CVE-2025-68623: Privilege escalation in n/a

> A low-privilege user can replace a downloaded executable during DirectX installation to execute arbitrary code with SYSTEM privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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 Mar 2026
- **Updated:** 11 Mar 2026
- **Also known as:** GHSA-jp8v-rp55-736m

## What is CVE-2025-68623?

CVE-2025-68623 is a high-severity vulnerability in n/a, published on 11 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Microsoft DirectX End-User Runtime Web Installer 9.29.1974.0, a low-privilege user can replace an executable file during the installation process, which may result in unintended elevation of privileges. During installation, the installer runs with HIGH integrity and downloads executables and DLLs to the %TEMP% folder - writable by standard users. Subsequently, the installer executes the downloaded executable with HIGH integrity to complete the application installation. However, an attacker can replace the downloaded executable with a malicious, user-controlled executable. When the installer executes this replaced file, it runs the attacker's code with HIGH integrity. Since code running at HIGH integrity can escalate to SYSTEM level by registering and executing a service, this creates a complete privilege escalation chain from standard user to SYSTEM. NOTE: The Supplier disputes this record stating that they have determined this to be the behavior as designed.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-68623 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68623 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68623 is a high-severity vulnerability in n/a, published on 11 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68623 exists.

Affected product: n/a. 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-68623/ (Markdown: https://insights.sbomify.com/CVE-2025-68623/index.md)
```

## Sources

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

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