# CVE-2024-39833: Privilege escalation in Intel(R) QAT software

> An authenticated local attacker can escalate privileges in Intel QAT software due to an uncontrolled search path vulnerability.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:A/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 May 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-cpqc-wrh6-wj8j

## What is CVE-2024-39833?

CVE-2024-39833 is a medium-severity vulnerability in Intel(R) QAT software, published on 13 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Uncontrolled search path for some Intel(R) QAT software before version 2.3.0 may allow an authenticated user to potentially enable escalation of privilege via local access.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2024-39833?


## How do I fix CVE-2024-39833?

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

## Is CVE-2024-39833 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-39833 and fix it if it is affected.

What it is: CVE-2024-39833 is a medium-severity vulnerability in Intel(R) QAT software, published on 13 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-39833 in the wild and no public exploit code.

Affected product: Intel(R) QAT software. 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-2024-39833/ (Markdown: https://insights.sbomify.com/CVE-2024-39833/index.md)
```

## Sources

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

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