CVE-2026-0436: AMD Secure Processor SPDM driver parameter sanitization

CVE-2026-0436 · Severity: info · Published 2026-11-12

The AMD Secure Processor's trusted execution environment includes an SPDM (Secure Protocol and Data Model) driver that does not adequately validate user-supplied input. An attacker could exploit this to compromise the security of the platform, leak sensitive memory contents, or cause the system to become unresponsive.

Vendors: Amd.

Quick answers

Is CVE-2026-0436 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-0436 being exploited in the wild.
How severe is CVE-2026-0436?
Informational severity, published 12 November 2026.
Which products and versions are affected?
AMD Secure Processor TEE SPDM driver.
Is there a fix for CVE-2026-0436?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-0436 attacked?
It is in device firmware.
Am I affected by CVE-2026-0436?
Check whether you run Amd Secure Processor TEE SPDM driver. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An insufficient input validation vulnerability exists in the AMD Secure Processor TEE SPDM driver, where malicious parameters are not properly sanitized before processing. This could allow an attacker to trigger memory corruption, information disclosure, or denial of service conditions depending on the attack vector and execution context.

Affected products

  • AMD Secure Processor TEE SPDM driver

Timeline

  • 2026-11-12: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.