# CVE-2024-0114: Privilege escalation in NVIDIA Hopper HGX 8-GPU

> A malicious actor with BMC admin access can escalate privileges to HMC administrator, enabling code execution and data tampering on NVIDIA HGX systems.

- **Severity:** High 8.1 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-qh47-4wjj-cqjj

## What is CVE-2024-0114?

CVE-2024-0114 is a high-severity vulnerability in NVIDIA Hopper HGX 8-GPU, published on 5 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA Hopper HGX for 8-GPU contains a vulnerability in the HGX Management Controller (HMC) that may allow a malicious actor with administrative access on the BMC to access the HMC as an administrator. A successful exploit of this vulnerability may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.

Weakness: CWE-1244 (Internal Asset Exposed to Unsafe Debug Access Level or State)

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


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

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

## Is CVE-2024-0114 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0114 is a high-severity vulnerability in NVIDIA Hopper HGX 8-GPU, published on 5 Mar 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-2024-0114 in the wild and no public exploit code.

Affected product: NVIDIA Hopper HGX 8-GPU. 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-0114/ (Markdown: https://insights.sbomify.com/CVE-2024-0114/index.md)
```

## Sources

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

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