dbcve.org
CWE-1327Weakness · CWE-1327

CVE-2026-0481

CRITICAL · 9.2 CVSS v4.0 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unrestricted IP address binding in the AMD Device Metrics Exporter (ROCm ecosystem) could allow a remote attacker to perform unauthorized changes to the GPU configuration, potentially resulting in loss of availability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Unrestricted IP address binding in the AMD Device Metrics Exporter (ROCm ecosystem) allows the service to listen on all network interfaces, enabling remote attackers to access the GPU configuration interface without authentication and modify settings, causing loss of availability.

MitigationBind the AMD Device Metrics Exporter to localhost (127.0.0.1) or specific trusted IP addresses, and implement authentication for the configuration API.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if AMD Device Metrics Exporter is installed
    Check for the amd_device_metrics_exporter process running on the system (e.g., ps aux | grep -i amd_metrics) or check for the binary in common ROCm installation paths such as /opt/rocm/bin/ or /usr/local/bin/
    Affected if The process or binary exists on the system
  2. Determine the service listening address
    Run 'netstat -tlnp' or 'ss -tlnp' and look for the port used by the AMD Device Metrics Exporter (common default ports include 9330 or 9340). Check the Local Address column to see if it shows 0.0.0.0, ::, or * instead of 127.0.0.1 or a specific IP
    Affected if The service is bound to 0.0.0.0, ::, or * (all interfaces) rather than 127.0.0.1 (localhost only)
  3. Inspect the service configuration file
    Locate the configuration file for AMD Device Metrics Exporter (commonly in /etc/ or within the ROCm configuration directory). Search for parameters related to binding address, listen address, host, or network interface
    Affected if The configuration specifies binding to all interfaces (0.0.0.0 or ::) or does not restrict binding to localhost
  4. Test network accessibility
    From a different host on the network, attempt to connect to the AMD Device Metrics Exporter port (e.g., curl http://target_ip:port/metrics or the configuration API endpoint). Also verify if the service responds to localhost connections
    Affected if The service is reachable from remote hosts without requiring local access or authentication
  5. Verify authentication requirements
    Review the configuration or documentation for the configuration API endpoints. Attempt to access the configuration interface (e.g., API endpoints for modifying GPU settings) without providing credentials
    Affected if The configuration API is accessible without any authentication mechanism or allows unauthored modifications

The system is affected if the AMD Device Metrics Exporter is running and bound to all network interfaces (0.0.0.0 or ::) rather than localhost (127.0.0.1) or a specific trusted IP, making the GPU configuration interface accessible to remote attackers without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Bind the AMD Device Metrics Exporter to localhost (127.0.0.1) or specific trusted IP addresses, and implement authentication for the configuration API.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0481 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0481 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data