# CVE-2026-0481: Misconfiguration in AMD Instinct™ MI210

> Remote attackers can modify GPU configurations via unrestricted IP binding in AMD Device Metrics Exporter, causing availability loss.

- **Severity:** Critical 9.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-g7c7-634v-gp3r

## What is CVE-2026-0481?

CVE-2026-0481 is a critical vulnerability in AMD Instinct™ MI210, published on 15 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-1327 (Binding to an Unrestricted IP Address)

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


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

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

## Is CVE-2026-0481 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0481 is a critical vulnerability in AMD Instinct™ MI210, published on 15 May 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-0481 in the wild and no public exploit code.

Affected product: AMD Instinct™ MI210. 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-0481/ (Markdown: https://insights.sbomify.com/CVE-2026-0481/index.md)
```

## Sources

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

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