Skip to main content
Mallory
UnratedVulnerability

CVE-2026-43613: AMD Secure Processor RPMC Update Verification Bypass

Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days8 mentions · peak 7 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-43613CWE-754

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

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.
Activity feed

Recent activity

8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
cyber security newsNews · Nov 18, 2026New Hello Again Attack Bypasses Windows Hello and BitLocker PIN Lockout ProtectionAn AMD Secure Processor firmware vulnerability, rated CVSS 5.1, in which RPMC counter increases are not properly verified. A physical interposer can suppress counter updates while reporting success, enabling rollback of fTPM state and bypass of PIN lockout protection. AMD plans firmware fixes for affected Ryzen, EPYC, and Athlon products, with some target dates in November 2026; the content does not confirm released patches. Interim mitigations include maintaining physical control, monitoring for tampering, and using longer PINs.Read more ↗cryptika blogNews · Nov 18, 2026New Hello Again Attack Bypasses Windows Hello and BitLocker PIN Lockout Protection | Cryptika CybersecurityAn AMD Secure Processor firmware flaw allows a physically present attacker to suppress replay-protected counter updates because the firmware fails to verify that an increment completed. Demonstrated as part of the broader Hello Again research, this enables rollback of fTPM lockout state and repeated Windows Hello or BitLocker PIN guesses. The research reduced a four-digit Windows Hello PIN attack to about 40 hours and a default six-digit BitLocker startup PIN attack to 20 days. AMD assigns the flaw a CVSS score of 5.1 and plans firmware fixes.Read more ↗the hacker newsNews · Nov 18, 2026New Attack Bypasses TPM Lockout to Crack Windows Hello and BitLocker PINs in Days, Not YearsAn AMD processor firmware flaw enables a physically present attacker to bypass firmware TPM lockout protections. An interposer blocks RPMC counter updates and reports success, which the firmware fails to verify. Restoring an earlier TPM state then resets failed-PIN counters, enabling faster guessing of Windows Hello and BitLocker PINs. Exploitation requires hardware access and specialized equipment. AMD assigns a CVSS score of 5.1; fixes are planned, but PC updates are not yet available according to the article.Read more ↗
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.