| CVE-2025-65829 | The ESP32 system on a chip (SoC) that powers the Meatmeet basestation device was found to lack Secure Boot. The Secure Boot feature ensures that only authenticated software can execute on the device. The Secure Boot process forms a chain of trust by verifying all mutable software entities involved in the Application Startup Flow. As a result, an attacker with physical access to the device can flash modified firmware to the device, resulting in the execution of malicious code upon startup. | medium | |
| CVE-2020-0689 | A security feature bypass vulnerability exists in secure boot, aka 'Microsoft Secure Boot Security Feature Bypass Vulnerability'. | medium | |
| CVE-2024-7344 | Howyar UEFI Application "Reloader" (32-bit and 64-bit) is vulnerable to execution of unsigned software in a hardcoded path. | high | |
| CVE-2024-20456 | A vulnerability in the boot process of Cisco IOS XR Software could allow an authenticated, local attacker with high privileges to bypass the Cisco Secure Boot functionality and load unverified software on an affected device. To exploit this successfully, the attacker must have root-system privileges on the affected device. This vulnerability is due to an error in the software build process. An attacker could exploit this vulnerability by manipulating the system’s configuration options to bypass some of the integrity checks that are performed during the booting process. A successful exploit could allow the attacker to control the boot configuration, which could enable them to bypass of the requirement to run Cisco signed images or alter the security properties of the running system. | medium | |
| CVE-2022-20826 | A vulnerability in the secure boot implementation of Cisco Secure Firewalls 3100 Series that are running Cisco Adaptive Security Appliance (ASA) Software or Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated attacker with physical access to the device to bypass the secure boot functionality. This vulnerability is due to a logic error in the boot process. An attacker could exploit this vulnerability by injecting malicious code into a specific memory location during the boot process of an affected device. A successful exploit could allow the attacker to execute persistent code at boot time and break the chain of trust. | medium | |
| CVE-2019-1294 | A security feature bypass exists when Windows Secure Boot improperly restricts access to debugging functionality, aka 'Windows Secure Boot Security Feature Bypass Vulnerability'. | medium | |
| CVE-2019-1368 | A security feature bypass exists when Windows Secure Boot improperly restricts access to debugging functionality, aka 'Windows Secure Boot Security Feature Bypass Vulnerability'. | medium | |
| CVE-2022-34302 | A flaw was found in New Horizon Datasys bootloaders before 2022-06-01. An attacker may use this bootloader to bypass or tamper with Secure Boot protections. In order to load and execute arbitrary code in the pre-boot stage, an attacker simply needs to replace the existing signed bootloader currently in use with this bootloader. Access to the EFI System Partition is required for booting using external media. | medium | |
| CVE-2024-26250 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-28922 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-28921 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-28896 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-28898 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-28903 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-26184 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-38011 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2025-2486 | The Ubuntu edk2 UEFI firmware packages accidentally allowed the UEFI Shell to be accessed in Secure Boot environments, possibly allowing bypass of Secure Boot constraints. Versions 2024.05-2ubuntu0.3 and 2024.02-2ubuntu0.3 disable the Shell. Some previous versions inserted a secure-boot-based decision to continue running inside the Shell itself, which is believed to be sufficient to enforce Secure Boot restrictions. This is an additional repair on top of the incomplete fix for CVE-2023-48733. | high | |
| CVE-2024-20669 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-28923 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-37969 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-37981 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-37972 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-37975 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-37977 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-37988 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-38065 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-26240 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-26168 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-29062 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-37970 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-37971 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-37989 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2025-21213 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2025-21215 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-26194 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2016-7247 | Microsoft Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, and 1607, and Windows Server 2016 allow physically proximate attackers to bypass the Secure Boot protection mechanism via a crafted boot policy, aka "Secure Boot Component Vulnerability." | high | |
| CVE-2022-1665 | A set of pre-production kernel packages of Red Hat Enterprise Linux for IBM Power architecture can be booted by the grub in Secure Boot mode even though it shouldn't. These kernel builds don't have the secure boot lockdown patches applied to it and can bypass the secure boot validations, allowing the attacker to load another non-trusted code. | high | |
| CVE-2024-20688 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-28919 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-28924 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-28897 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-28899 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-37978 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-38010 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2022-21894 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-20689 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-28920 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-26171 | Secure Boot Security Feature Bypass Vulnerability | medium | |
| CVE-2024-26175 | Secure Boot Security Feature Bypass Vulnerability | high | |
| CVE-2024-26180 | Secure Boot Security Feature Bypass Vulnerability | high | |
