# CVE-2026-0438: Code injection in AMD EPYC™ 4004 Series Processors

> A privileged attacker can execute arbitrary code in System Management Mode on AMD processors, compromising system security.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:P/AC:H/AT:P/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 May 2026
- **Updated:** 19 May 2026
- **Also known as:** GHSA-783m-hm3h-gh75

## What is CVE-2026-0438?

CVE-2026-0438 is a medium-severity code injection vulnerability in AMD EPYC™ 4004 Series Processors, published on 15 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A System Management Mode (SMM) handler could perform a callout to code located in non-SMM/untrusted memory. A highly privileged attacker could, with active user interaction and under high complexity and present preconditions, trigger execution of attacker-controlled code in SMM, potentially compromising the system’s confidentiality, integrity, and availability.

Weakness: CWE-1072 (Data Resource Access without Use of Connection Pooling)

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


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

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

## Is CVE-2026-0438 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0438 is a medium-severity code injection vulnerability in AMD EPYC™ 4004 Series Processors, published on 15 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-0438 in the wild and no public exploit code.

Affected product: AMD EPYC™ 4004 Series Processors. 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-0438/ (Markdown: https://insights.sbomify.com/CVE-2026-0438/index.md)
```

## Sources

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

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