UEFI firmware is widely deployed across PCs/servers; Secure Boot bypass enables boot‑time persistence and broad impact across organizations.
CVE-2026-6485
UEFI embedded Shell enables Secure Boot bypass via shell commands/startup scripts.
Is CVE-2026-6485 being exploited?
Not confirmed. CVE-2026-6485 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.12% probability of exploitation in the next 30 days.
How severe is CVE-2026-6485?
CVE-2026-6485 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-6485?
Yes. A fix has been recorded for CVE-2026-6485. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-6485 affect?
CVE-2026-6485 affects UEFI firmware with embedded Shell (e.g., Insyde), OEM PCs and servers exposing UEFI Shell. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-6485?
Apply vendor firmware updates, disable UEFI Shell, restrict BIOS/physical access, enforce firmware passwords.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Bypass Secure Boot to load unsigned bootloaders/UEFI malware, enabling persistent boot‑time compromise and full OS takeover.
Immediate action required
- affectedSee in the Solution
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.