# CVE-2025-54504: AMD SEV firmware access control bypass in trusted region

Source: https://junglewise.ai/threats/cve-2025-54504-insufficient-granularity-of-access-control-in-amd-secure  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2025-54504 · Severity: info · Published 2026-11-10

AMD Secure Encrypted Virtualization (SEV) firmware contains an access control weakness that allows an administrator to write to a protected memory region used by SEV-Encrypted State (SEV-ES). This could enable an attacker with admin privileges to tamper with virtualization security guarantees, compromising the integrity of encrypted virtual machines.

Technologies: [Amd Secure Encrypted Virtualization (SEV) firmware](https://junglewise.ai/threats/technologies/secure-encrypted-virtualization-sev-firmware). Vendors: [Amd](https://junglewise.ai/threats/vendors/amd).

## Quick answers

**Is CVE-2025-54504 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-54504 being exploited in the wild.

**How severe is CVE-2025-54504?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** AMD Secure Encrypted Virtualization (SEV) firmware.

**Is there a fix for CVE-2025-54504?** 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-2025-54504 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2025-54504?** Check whether you run Amd Secure Encrypted Virtualization (SEV) firmware. 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

Insufficient granularity of access control in AMD SEV firmware fails to adequately restrict write access to a trusted region used by SEV-ES, allowing an attacker with administrative privileges to modify protected state. This is a firmware-level vulnerability requiring local privileged access to exploit, potentially breaking the integrity assurances of SEV-encrypted virtual machines.

## Affected products

- AMD Secure Encrypted Virtualization (SEV) firmware

## Timeline

- 2026-11-10: disclosed

## References

- [https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-3037.html](https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-3037.html)

## Related threats

- [AMD Secure Encrypted Virtualization firmware use-after-free](https://junglewise.ai/threats/cve-2026-0435-operation-on-a-resource-after-expiration-or-release-in-the-amd)
- [AMD SEV firmware downgrade in ASP Bootloader](https://junglewise.ai/threats/cve-2026-0003-use-of-a-per-part-static-key-in-the-asp-bootloader-could-allow-an)
- [AMD Secure Encrypted Virtualization off-by-one error in firmware](https://junglewise.ai/threats/cve-2026-40669-an-off-by-one-error-in-amd-secure-encrypted-virtualization-sev)
- [AMD Secure Encrypted Virtualization SEV firmware integrity weakness](https://junglewise.ai/threats/cve-2026-28248-improper-enforcement-of-behavioral-workflow-in-amd-secure)
