CVE-2026-43613: AMD Secure Processor RPMC Update Verification Bypass
CVE-2026-43613 is an insufficient verification vulnerability in AMD Secure Processor firmware that fails to confirm completion of Replay Protected Monotonic Counter (RPMC) increments. A physically present attacker can interpose between the processor and motherboard flash, suppress counter increments, and falsely indicate successful completion. This allows previously saved firmware TPM state to be accepted despite rollback protections, enabling restoration of failed-PIN counters and circumvention of TPM anti-hammering protections. The vulnerability was investigated as part of the Hello Again research and has an AMD-assigned CVSS score of 5.1. It is distinct from the separately demonstrated Winbond flash authentication-key disclosure weakness.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Rolling back firmware TPM state undermines PIN-guessing rate limits protecting Windows Hello and BitLocker TPM+PIN configurations. Repeatedly restoring earlier failed-attempt counters permits continued guessing without the intended TPM lockout delays. Successful PIN recovery can enable Windows sign-in or access to BitLocker-protected data, depending on the targeted configuration. A recovered Windows Hello PIN may also unlock device-bound credentials and enterprise single sign-on access. Exploitation requires physical tampering; exploitation outside laboratory settings has not been described.
Mitigation
If you can’t patch tonight, do this now.
Maintain physical control of affected devices and investigate signs of motherboard or flash tampering. Increase Windows Hello and BitLocker minimum PIN lengths, preferably by at least two digits, and enable longer enhanced alphanumeric BitLocker startup PINs where appropriate. Each additional decimal digit increases the search space tenfold. These measures increase guessing costs but do not correct the firmware flaw. Treat theft of an affected device containing sensitive data as a potential exposure even when its drive is encrypted.
Remediation
Patch, then assume compromise.
Install applicable system-vendor firmware updates incorporating AMD's correction for RPMC increment-completion verification, following AMD security bulletin AMD-SN-7079. AMD scheduled firmware fixes for covered Ryzen, Ryzen AI, Ryzen Threadripper, Athlon, and EPYC products between November 2026 and February 2027, with one product lacking a target date. These dates concern AMD firmware delivery and do not establish availability of corresponding OEM updates. Exact fixed firmware versions and protection against reinstalling older vulnerable firmware are not available.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-43613 exploited in the wild?
- As of Nov 22, 2026, Mallory has no reports of CVE-2026-43613 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-43613?
- As of Nov 22, 2026, Mallory has found no public exploit for CVE-2026-43613.
- Is there a patch for CVE-2026-43613?
- Install applicable system-vendor firmware updates incorporating AMD's correction for RPMC increment-completion verification, following AMD security bulletin AMD-SN-7079. AMD scheduled firmware fixes for covered Ryzen, Ryzen AI, Ryzen Threadripper, Athlon, and EPYC products between November 2026 and February 2027, with one product lacking a target date.
Recent activity
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.