Quick answers
- Is CVE-2026-0003 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-0003 being exploited in the wild.
- How severe is CVE-2026-0003?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- AMD Secure Encrypted Virtualization (SEV) firmware.
- Is there a fix for CVE-2026-0003?
- 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-0003 attacked?
- It is attacked over the network or with physical access, in device firmware.
- Am I affected by CVE-2026-0003?
- 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
The ASP (AMD Secure Processor) Bootloader uses a per-part static key for firmware signing, enabling firmware downgrade attacks. An attacker with physical access or network position to intercept firmware updates could roll back SEV firmware to versions with known decryption vulnerabilities. This is a cryptographic weakness in the firmware update mechanism rather than a memory corruption or authentication bypass.
Affected products
- AMD Secure Encrypted Virtualization (SEV) firmware
Timeline
- 2026-11-10: disclosed