AMD fTPM Vulnerabilities: Update Your BIOS to Fix CVE-2026-6726
AMD has disclosed two high-severity vulnerabilities affecting its firmware-based Trusted Platform Module (fTPM) 2.0 implementation across a broad range of processors.
Tracked as CVE-2026-6726 and CVE-2026-6727, the vulnerabilities carry CVSS scores of 8.5 and 8.3, respectively. The flaws affect the TPM 2.0 reference implementation used by AMD fTPM for cryptographic operations involving keys, certificates, and platform attestation.
AMD began distributing firmware fixes to motherboard and system manufacturers in May 2026. Updated BIOS releases have subsequently appeared across AMD’s AM4 and AM5 platforms, meaning systems that received a recent BIOS update may already contain the required mitigation.
The vulnerabilities require local access with elevated privileges, which significantly reduces the immediate risk to typical consumer systems. However, the attack requirements are less reassuring in enterprise, managed-device, remote-attestation, and data-center environments where privileged local access can have substantially greater consequences.
🔐 Two High-Severity TPM 2.0 Vulnerabilities #
The vulnerabilities reside in the TPM 2.0 reference code used by AMD’s fTPM implementation.
Firmware TPM provides hardware-backed security functions without requiring a discrete TPM chip. It can protect cryptographic keys, support device authentication, enable secure boot-related workflows, and provide platform attestation to establish trust in a system’s hardware and software state.
A vulnerability in the underlying TPM implementation can therefore affect security mechanisms that depend on those guarantees.
CVE-2026-6726: TPM Key Information Leakage #
CVE-2026-6726 carries a CVSS score of 8.5.
The vulnerability involves information leakage that could allow an attacker to obtain credentials associated with a falsified TPM key.
An attacker able to exploit the flaw could potentially use the recovered information to construct forged TPM 2.0 attestations.
This is particularly significant for environments that rely on TPM-based attestation to verify the integrity or identity of a computing platform before granting access to protected resources.
CVE-2026-6727: RSA-OAEP Timing Side Channel #
CVE-2026-6727 carries a CVSS score of 8.3.
The issue is a timing side-channel vulnerability affecting RSA-OAEP decryption.
By analyzing timing behavior during cryptographic operations, an attacker could potentially recover information about protected data and decrypt ciphertexts handled by the TPM.
Side-channel vulnerabilities are particularly relevant to security-sensitive environments because the cryptographic operation itself may remain mathematically sound while observable execution characteristics leak information about the underlying secret.
⚠️ Local Privilege Requirements Reduce the Immediate Attack Surface #
Despite the high CVSS scores, neither vulnerability represents a straightforward remote attack against an unprotected consumer PC.
Both vulnerabilities require an attacker to have local access with elevated privileges, including privileged access to the TPM command interface.
That requirement substantially changes the practical threat model.
An attacker generally cannot exploit these vulnerabilities simply by knowing a system’s IP address or sending a malicious network packet. They first need an appropriate level of local privileged access.
Why Enterprise Systems Face Greater Risk #
The local-privilege requirement is less reassuring in environments where attackers may already have partial control over endpoints or infrastructure.
Potentially higher-risk scenarios include:
- Enterprise endpoint fleets
- Managed corporate systems
- Remote-attestation infrastructure
- Virtualized environments
- Security-sensitive development systems
- Data-center platforms
- Systems using TPM-based identity or integrity verification
In these environments, TPM functionality can play a role in establishing trust between machines and services. A compromised TPM trust boundary can therefore have consequences beyond a single endpoint.
For typical home users, the immediate exploitation path is considerably narrower. Nevertheless, the appropriate mitigation remains the same: install the latest firmware provided by the motherboard or system manufacturer.
🧩 AMD Processors Affected by the fTPM Issues #
AMD’s advisory covers a broad range of processors using the affected fTPM reference architecture.
Affected product families include:
| Platform | Affected Families |
|---|---|
| Desktop | Ryzen 3000 through Ryzen 9000 |
| High-end desktop | Ryzen 9 9950X3D and other supported Ryzen processors |
| Mobile | Ryzen AI 300 and Ryzen AI 400 |
| Handheld | Ryzen Z1 and Ryzen Z2 |
| Workstation | Threadripper |
| Enterprise | EPYC 4005 |
| Embedded | Ryzen Embedded 5000 |
| Budget mobile | Athlon 3000-series mobile |
The breadth of the affected processor generations makes motherboard firmware availability particularly important.
A processor can remain vulnerable even when AMD has already developed a fix if the corresponding AGESA update has not yet been integrated into the BIOS or firmware distributed by the system manufacturer.
Why Processor Age Does Not Necessarily Protect Against the Issue #
The vulnerability is associated with the fTPM implementation rather than a single newly introduced CPU architecture.
As a result, affected systems span multiple AMD generations and product segments.
Users should therefore avoid assuming that an older platform is unaffected simply because it predates recent Ryzen generations.
The correct approach is to identify the exact motherboard or OEM system model and verify its latest available firmware.
🛠️ AMD Delivered AGESA Fixes to Manufacturers #
AMD began providing updated AGESA platform initialization code to OEMs and motherboard manufacturers in May 2026.
Examples of affected firmware branches include:
ComboAM4PI 1.0.0.11ComboAM5PI 1.2.0.3kComboAM5PI 1.3.0.1b
AGESA is AMD’s low-level firmware component used by motherboard manufacturers as part of their BIOS implementation.
The security fix therefore does not normally arrive as a standalone Windows patch. Instead, it is integrated into updated motherboard or system firmware.
BIOS Updates Are the Primary Mitigation #
Major motherboard manufacturers, including ASUS, MSI, Gigabyte, and ASRock, have released BIOS updates incorporating patched firmware for affected AM4 and AM5 systems.
The exact BIOS version depends on the motherboard model, processor generation, and vendor firmware branch.
Users should therefore avoid applying a BIOS file intended for a different motherboard revision or platform.
🔎 How to Check Whether Your System Is Patched #
The most reliable way to determine whether a system has received the fTPM mitigation is to check the BIOS version against the latest firmware published by the motherboard or system manufacturer.
1. Identify the Motherboard or System Model #
On a custom-built desktop, determine the exact motherboard model and revision.
On an OEM laptop, desktop, or workstation, use the system manufacturer’s model identifier instead.
Firmware packages are hardware-specific, so the exact model matters.
2. Check the Manufacturer’s Support Page #
Open the motherboard or system manufacturer’s official support page and locate the BIOS or firmware downloads for the exact model.
Look for firmware released after the vendor incorporated AMD’s security fixes.
Security advisories or BIOS release notes may explicitly reference the relevant vulnerability, AGESA version, TPM fixes, or security updates.
3. Compare Your Current BIOS Version #
Check the BIOS version currently installed on the system and compare it with the latest version available from the manufacturer.
If the installed version predates the patched release, update the firmware according to the manufacturer’s instructions.
4. Avoid Interrupting the Firmware Update #
BIOS updates should be performed with a stable power source and according to the motherboard vendor’s documented procedure.
Do not interrupt the update process or power off the system while firmware is being written.
For enterprise systems, firmware deployment should follow the organization’s normal change-management and validation process.
🔒 Why fTPM Security Matters #
TPM technology is increasingly integrated into modern operating-system and enterprise security architectures.
TPM-backed functions can support:
- Cryptographic key storage
- Device identity
- Platform attestation
- Secure boot workflows
- Credential protection
- Disk-encryption key protection
- Hardware-backed authentication
A vulnerability that undermines TPM key material or attestation can therefore affect security assumptions that extend beyond ordinary application-level vulnerabilities.
The practical impact depends heavily on how a particular system uses fTPM and what privileges an attacker already possesses.
This is why the CVSS scores should not be interpreted as meaning that every affected PC is equally exposed to remote compromise.
📊 High Severity Does Not Mean Universal Remote Exploitation #
The combination of an 8.5 and 8.3 CVSS score warrants prompt patching, but the scores need to be considered alongside the attack prerequisites.
The vulnerabilities require local, elevated privileges, creating a significantly higher barrier than a remotely exploitable network vulnerability.
For a typical personal computer that is otherwise well secured, the immediate risk is relatively limited.
However, an attacker who has already obtained privileged access may be able to use the TPM vulnerabilities to undermine security properties that would otherwise remain protected.
That makes patching particularly important for systems where TPM-based attestation or cryptographic trust is part of a larger security architecture.
🚨 BIOS Updates Should Be Treated as the Fix #
The most important takeaway is simple: check your BIOS firmware.
AMD has already supplied the necessary platform-level fixes to motherboard and system manufacturers. The remaining step is for those updates to reach affected systems.
If your motherboard BIOS has been updated recently, there is a good chance the required AGESA changes are already included. Nevertheless, users should verify the firmware release notes rather than relying solely on the installation date.
For systems that have not received a recent BIOS update, the recommended action is to obtain the latest firmware directly from the motherboard or OEM manufacturer.
Because the affected processor range extends from older Ryzen generations through current Ryzen AI, Threadripper, EPYC, and embedded platforms, checking firmware availability is more reliable than assuming a particular CPU generation is safe.
AMD’s fTPM vulnerabilities demonstrate an important aspect of modern platform security: trusted computing features are only as strong as the firmware implementing them. Keeping motherboard firmware current is therefore not merely a compatibility or performance task—it is an essential part of maintaining the system’s security boundary.