Skip to main content
Mallory
UnratedVulnerability

CVE-2026-40671: Skyfall

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

Skyfall is an incomplete-cleanup vulnerability in AMD VMRUN error handling that exposes SEV-SNP confidential-virtual-machine register data through a Transient Scheduler Attacks (TSA) side channel. A malicious host hypervisor can deliberately cause VM entry to fail after the processor has cached part of the guest's saved state. Residual state is not adequately cleared and can subsequently be recovered through transient-execution timing. AMD lists EPYC 7003, 8004, 8005, 9004, and 9005 server processors as affected; researchers demonstrated leakage on Zen 3 and Zen 4 processors. The vulnerability is rated Medium, with a severity score of 4.9.

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.

Successful exploitation compromises the confidentiality of SEV-SNP guest register data despite isolation from the host hypervisor. Sensitive values can include cryptographic keys when they occupy exposed registers. Researchers recovered a disk-encryption key from a test guest modified to pause while the key was in registers; equivalent extraction from an unmodified guest requires suitable execution-state targeting. Arbitrary guest-memory modification and attestation forgery are not established consequences of this CVE.

Mitigation

If you can’t patch tonight, do this now.

No vendor-supported workaround is identified. Confidential-computing tenants should coordinate with their provider to confirm host remediation and, where patch-level attestation information is available, enforce minimum trusted firmware and microcode versions before releasing secrets. Attestation policy changes do not substitute for installing the host fix.

Remediation

Patch, then assume compromise.

Obtain and deploy the server manufacturer's firmware or BIOS update incorporating AMD's Skyfall microcode mitigation for the specific processor and platform. Host operators and cloud providers must perform remediation; guest operating-system updates alone cannot correct the flaw. Update availability is platform-dependent: AMD's vulnerability-specific advisory describes planned mitigations without a fixed version or release schedule, while platform reporting identifies released or scheduled updates. Verify availability and installation with the system manufacturer rather than assuming every affected platform is already patched.

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-40671 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-40671 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-40671?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-40671.
Is there a patch for CVE-2026-40671?
Obtain and deploy the server manufacturer's firmware or BIOS update incorporating AMD's Skyfall microcode mitigation for the specific processor and platform. Host operators and cloud providers must perform remediation; guest operating-system updates alone cannot correct the flaw.
Activity feed

Recent activity

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

View more in app →
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 activity3Community discussion across Reddit, Mastodon, and other social sources.