Secure Boot bypass via exposed UEFI Shell
Published Nov 26, 2025 · Updated Nov 26, 2025
Secure Boot bypass in Ubuntu EDK II allows local users to access the AAVMF UEFI Shell in affected aarch64 virtual machines. The Ubuntu AAVMF firmware image includes and launches the built-in UEFI Shell while Secure Boot is enabled instead of disabling that component. Reachability requires active local interaction with a Secure Boot-enabled aarch64 virtual machine; shell access can bypass boot restrictions and alter protected state.
Summary
What happened
Secure Boot bypass in Ubuntu EDK II allows local users to access the AAVMF UEFI Shell in affected aarch64 virtual machines. The Ubuntu AAVMF firmware image includes and launches the built-in UEFI Shell while Secure Boot is enabled instead of disabling that component. Reachability requires active local interaction with a Secure Boot-enabled aarch64 virtual machine; shell access can bypass boot restrictions and alter protected state.
The record
- CVE
- CVE-2025-2486
- Published
- Nov 26, 2025
- Updated
- Nov 26, 2025
- Vendor
- TianoCore
- Product
- EDK II
- Classifications
- CWE-489
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 26, 2025CVE publishedPublication date reported by the CVE source.
- Nov 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2024.02 <2024.02-2ubuntu0.3
- Affected versionversion=2024.05 <2024.05-2ubuntu0.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo