Skip to main content
Mallory
MediumVulnerability

CVE-2026-18448: Skyfall SMM Information Disclosure in EDK II

Published Nov 10, 2026 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS5.6Medium · v4
EPSS0.13%3rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-18448CWE-1420

CVE-2026-18448 is a transient-execution information disclosure vulnerability in EDK II BIOS firmware caused by missing Transient Scheduler Attack mitigations. A privileged local attacker can exploit the weakness to disclose System Management RAM (SMRAM) contents, including saved register values associated with System Management Mode (SMM). The vulnerability represents the SMM disclosure component of Skyfall and is distinct from its separately tracked confidential-VM disclosure vulnerability. Affected platforms include AMD EPYC and Ryzen systems, including embedded models.

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 breaches the confidentiality of SMRAM, potentially exposing sensitive register values and other protected SMM data to privileged local software outside SMM. The vulnerability is assessed as having high confidentiality impact, with no identified integrity or availability impact.

Mitigation

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

Apply AMD's previously recommended Transient Scheduler Attack mitigations where applicable while awaiting the EDK II firmware fix. These measures are recommended alongside the EDK II patch, not established as a universal substitute; for five affected EPYC server series, the guidance lists only the forthcoming patch.

Remediation

Patch, then assume compromise.

Install platform-vendor BIOS or UEFI firmware incorporating the EDK II fix for CVE-2026-18448 when available. Platform firmware addressing the issue is available for some processors, including EPYC 4004 and 4005; updates for five affected EPYC server series were targeted for November 2026. No patched upstream EDK II version is identified. Confirm availability and deployment requirements with the system manufacturer rather than assuming an operating-system edk2 package update resolves the platform firmware exposure.

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-18448 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-18448 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-18448?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-18448.
Is there a patch for CVE-2026-18448?
Install platform-vendor BIOS or UEFI firmware incorporating the EDK II fix for CVE-2026-18448 when available. Platform firmware addressing the issue is available for some processors, including EPYC 4004 and 4005; updates for five affected EPYC server series were targeted for November 2026.
How severe is CVE-2026-18448?
CVE-2026-18448 has a CVSS v4 score of 5.6 (Medium) and an EPSS score of 0.13% (3rd percentile) as of Nov 16, 2026.
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 activityCommunity discussion across Reddit, Mastodon, and other social sources.