# Nvidia DCGM Exporter unauthenticated denial-of-service via /debug/pprof (CVE-2026-47483)

> A high-severity flaw (CVSS 8.2) in NVIDIA DCGM Exporter, the Prometheus exporter for GPU health and performance metrics, lets unauthenticated network attackers exhaust memory and crash the exporter by sending many concurrent requests to its Go /debug/pprof endpoints. The crash blinds GPU monitoring and the resource pressure can affect co-located AI training or inference workloads. NVIDIA lists DCGM Exporter 4.8.2 as the updated version. No in-the-wild exploitation or public PoC has been reported.

- **Published:** 2026-10-08T00:00:00Z
- **Last reviewed:** 2026-10-08T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-3057
- **ID:** TL-2026-3057
- **Severity:** HIGH (CVSS 8.2)
- **Category:** VULNERABILITY
- **Status:** PATCHED
- **Detections:** 9 · **IOCs:** 12 (full data via the Threadlinqs MCP server — Purple tier)
- **CVEs:** CVE-2026-47483

## Description

CVE-2026-47483 affects the /debug/pprof endpoints of NVIDIA DCGM Exporter, which are Go runtime profiling handlers served alongside the /metrics endpoint (default port 9400, plaintext HTTP, no authentication). Some pprof endpoints keep each request open for a caller-specified duration, so many concurrent unauthenticated profiling requests drive memory consumption up until the exporter runs out of memory and crashes. NVIDIA classifies the weakness as CWE-770 (Allocation of Resources Without Limits or Throttling) and scores it CVSS v3.1 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H); NVD/INCIBE note possible denial of service and information disclosure. The researchers at Lava reproduced the behavior against NVIDIA's official, unmodified container; no PoC was published and they state they did not test against public deployments.

Impact is twofold. First, availability: a crashed exporter removes GPU health visibility (utilization, memory, power, XID errors), and the CPU/RAM pressure can slow the host and interfere with co-located training or inference jobs, especially when no resource limits are set. Second, exposure: the exposed metrics already disclose GPU model, utilization, memory use, power, NVLink traffic, XID errors, driver versions and Kubernetes pod, namespace and container labels.

Lava's Shodan-based scans (four scans, March-May 2026) found about 2,100 GPU servers across roughly 300 organizations exposing DCGM Exporter metrics to the internet without authentication, covering more than 12,000 GPU UUIDs (about 44% / 5,274 in the US, hardware including B300, H200, H100, RTX 5090 and RTX 4090). About 25% of exposed DCGM hosts also exposed Go /debug/pprof/ endpoints. Lava also found 12,096 publicly exposed Prometheus Node Exporter hosts leaking server model, OS, firmware, hostnames, storage paths and networking hardware. Providers named as having customer infrastructure exposed were Nebius, Voltage Park, Lambda, Northern Data and DigitalOcean; Lava reported the findings and the providers worked with customers to fix the exposures.

NVIDIA's bulletin (answer 5857, first released 2026-07-28, last updated 2026-09-03) lists DCGM Exporter 0.0 to 4.8.2 as affected with 4.8.2 as the updated version (the bulletin's range and fix overlap, so confirm against the current bulletin), and DCGM 0.0 to 4.5.2 affected with 4.5.3 fixed. Per Lava, profiling is opt-in in current versions via --enable-pprof. Mitigations: upgrade, bind exporters to loopback or a private interface, firewall to authorized monitoring infrastructure only, protect Prometheus the same way, do not enable --enable-pprof unless required, and set resource limits. The Register reports no observed in-the-wild exploitation.

## MITRE ATT&CK

- T1596.005 Scan Databases
- T1595.002 Vulnerability Scanning
- T1592.001 Hardware
- T1592.002 Software
- T1190 Exploit Public-Facing Application
- T1613 Container and Resource Discovery
- T1499.004 Application or System Exploitation

## Sources

- [High-severity Nvidia bug could crash GPU monitoring on exposed servers](https://www.theregister.com/security/2026/10/08/high-severity-nvidia-bug-could-crash-gpu-monitoring-on-exposed-servers/5302077)
- [NVIDIA Security Bulletin: NVIDIA DCGM Exporter (answer 5857)](https://nvidia.custhelp.com/app/answers/detail/a_id/5857)
- [NVD: CVE-2026-47483](https://nvd.nist.gov/vuln/detail/CVE-2026-47483)
- [Lava research: CVE-2026-47483 Nvidia DCGM Exporter vulnerability](https://lava.security/research/cve-2026-47483-nvidia-dcgm-exporter-vulnerability)
- [INCIBE-CERT early warning: CVE-2026-47483](https://www.incibe.es/en/incibe-cert/early-warning/vulnerabilities/cve-2026-47483)
- [NVIDIA product-security repository, bulletin 5857](https://github.com/NVIDIA/product-security/tree/main/2026/5857)
- [CVE.org record: CVE-2026-47483](https://www.cve.org/CVERecord?id=CVE-2026-47483)
- [NixOS security tracker: NIXPKGS-2026-2306](https://tracker.security.nixos.org/issues/NIXPKGS-2026-2306)

## Full data

Detection queries (Splunk SPL / Microsoft KQL / Sigma) and IOC values require the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-3057