# CVE-2026-47483: Denial of service in DCGM

> Unauthenticated attackers can cause denial of service and information disclosure via concurrent requests to debug profiling endpoints in NVIDIA DCGM Exporter.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-ggq3-jj9v-85ww

## What is CVE-2026-47483?

CVE-2026-47483 is a high-severity denial of service vulnerability in NVIDIA DCGM, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NVIDIA DCGM Exporter for all platforms contains a vulnerability in the /debug/pprof endpoints, where an attacker could cause uncontrolled resource consumption by submitting concurrent unauthenticated profiling requests. A successful exploit of this vulnerability might lead to denial of service and information disclosure.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-47483?


## How do I fix CVE-2026-47483?

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

## Is CVE-2026-47483 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47483 and fix it if it is affected.

What it is: CVE-2026-47483 is a high-severity denial of service vulnerability in NVIDIA DCGM, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47483 in the wild and no public exploit code.

Affected product: NVIDIA DCGM. 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-2026-47483/ (Markdown: https://insights.sbomify.com/CVE-2026-47483/index.md)
```

## Sources

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

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