A flaw was found in QEMU. The VAPIC setup hypercall in hw/i386/vapic.c does not validate that the writable RAM alias remains within the option ROM window. A privileged guest user on a Q35/KVM machine can position this alias over locked SMRAM, bypassing chipset D_LCK protection and injecting code into System Management Mode memory.
CVE-2026-81627
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EG Risk
- 53(Track*)EG Risk 53/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity82% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 8%
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 21, 2026
Advisory Details (3)
Auto-updated Sep 18, 2026VAPIC writable ROM alias can escape the option-ROM window and expose locked SMRAM (#4206) · Issues · QEMU / QEMU · GitLab
https://gitlab.com/qemu-project/qemu/-/work_items/42062536950 – (CVE-2026-81627) CVE-2026-81627 qemu-kvm: VAPIC writable ROM alias can escape the option-ROM window and expose locked SMRAM
https://bugzilla.redhat.com/show_bug.cgi?id=2536950CVE-2026-81627 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2026-81627Vendor Advisories for CVE-2026-81627(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 32× in last 7d / 35× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-25 06:55 UTCGHSA enrichment
- 2026-09-24 19:37 UTCEG score recompute
- 2026-09-24 19:37 UTCGHSA enrichment
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-24 08:19 UTCGHSA enrichment
- 2026-09-23 21:01 UTCEG score recompute
- 2026-09-23 21:01 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 09:43 UTCGHSA enrichment
- 2026-09-22 22:25 UTCEG score recompute
- 2026-09-22 22:25 UTCGHSA enrichment
- 2026-09-22 16:01 UTCEPSS rescore
- 2026-09-22 11:06 UTCGHSA enrichment
- 2026-09-21 23:48 UTCEG score recompute
- 2026-09-21 23:48 UTCGHSA enrichment
- 2026-09-21 21:09 UTCEPSS rescore
- 2026-09-21 12:30 UTCEG score recompute
- 2026-09-21 12:30 UTCGHSA enrichment
- 2026-09-21 11:45 UTCGHSA enrichment
- 2026-09-21 11:25 UTCEG score recompute▲ 1.50
- 2026-09-21 11:25 UTCGHSA enrichment
- 2026-09-21 11:25 UTCMITRE cvelistV5CVSS v3 → 8.2 · severity → HIGH
- 2026-09-20 23:33 UTCEG score recompute
- 2026-09-20 23:33 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
Show 10 moreShow fewer
- 2026-09-19 21:20 UTCEG score recompute
- 2026-09-19 21:20 UTCGHSA enrichment
- 2026-09-18 19:08 UTCGHSA enrichment
- 2026-09-18 16:27 UTCEG score recompute
- 2026-09-18 16:27 UTCGHSA enrichment
- 2026-09-18 15:25 UTCEG score recompute
- 2026-09-18 15:25 UTCGHSA enrichment
- 2026-09-18 11:20 UTCEG score recompute
- 2026-09-18 11:04 UTCEG score recompute
- 2026-09-18 11:04 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-81627?
When was CVE-2026-81627 disclosed?
Is CVE-2026-81627 actively exploited?
What is the CVSS score of CVE-2026-81627?
How do I remediate CVE-2026-81627?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81627
Is Your Infrastructure Affected by CVE-2026-81627?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.