Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7
Tag: firmware (6 articles)Clear

Coldcard wallet firmware flaw let attackers guess seeds and steal 70 million dollars

A firmware flaw in Coldcard Bitcoin hardware wallets let attackers reconstruct wallet seeds offline and sweep roughly 70 million dollars from 1,196 addresses in 41 minutes on July 30. A March 2021 build error routed seed generation to a weak software random number generator instead of the device's hardware one, because the check confirmed a configuration macro existed rather than that it was enabled. That collapsed the randomness behind seeds to as little as 40 bits on older models, letting an attacker who can constrain the device identifier and timer state reproduce candidate seeds and match them to funded addresses. Coinkite shipped emergency firmware, but updating does not repair an already-generated seed.

Check
If you use a Coldcard wallet, check whether your seed was generated on affected firmware, and if so, generate a new wallet on patched firmware and move funds to fresh addresses.
Affected
Coldcard hardware wallet users whose seeds were generated on affected firmware from March 2021 onward; the weak randomness lets attackers reconstruct seeds offline and drain funds.
Fix
Generate a new seed on patched firmware and move funds to new addresses, treat any wallet made on affected firmware as compromised, and verify hardware RNGs are enabled, not just present.

Old Microsoft-signed Linux boot files let attackers bypass Secure Boot on most PCs

Researchers at ESET found 11 old Microsoft-signed Linux boot components, called shims, that can be used to bypass UEFI Secure Boot on almost any PC, regardless of its operating system. The trick needs no new vulnerability: because these shims were signed years ago with a trusted Microsoft certificate and never revoked, an attacker with admin or boot-level access can copy an old vulnerable shim onto a machine and run untrusted code before the operating system loads. That enables stealthy bootkits that survive reinstalls and start before security tools. Microsoft revoked all 11 in June by blocklisting their hashes, which Windows applies automatically and Linux systems can pull through firmware updates.

Check
Confirm the June UEFI revocation update reached your systems: Windows applies it automatically, while Linux hosts should pull it through the firmware update service, and use ESET's check for the revoked hashes.
Affected
Almost any UEFI-based computer trusting Microsoft's third-party 2011 certificate (CVE-2026-8863, CVE-2026-10797), regardless of operating system; an attacker with boot-level access can load an old signed shim to defeat Secure Boot.
Fix
Apply the UEFI revocation update on Windows and Linux, disable third-party UEFI signing where it is not needed, consider Secured-core hardware, and protect against the admin access these attacks require.

Six U-Boot bootloader flaws could run code before a device checks its firmware

Researchers at Binarly found six flaws in U-Boot, the open-source bootloader inside routers, IoT devices, industrial systems, and the management chips of data-center servers. All six are triggered while U-Boot is still reading an untrusted firmware image, before it verifies the signature, so an attacker who supplies a malicious image can act before the trust check runs. Two of the flaws can lead to arbitrary code execution at boot, undermining the whole chain of trust, while the other four crash the device. The vulnerable code dates back to 2013, affecting many releases and vendor forks. Exploiting them does not always need physical access: a compromised management interface could push a malicious image.

Check
Identify devices built on U-Boot, especially servers with baseboard management controllers and networking or IoT gear, and check with vendors whether firmware updates addressing these flaws are available or planned.
Affected
Devices using U-Boot, including many routers, IoT and industrial systems, and server management controllers; malicious firmware images can crash them or run code at boot before the signature is verified.
Fix
Apply vendor firmware updates as they incorporate the upstream fixes, restrict and monitor access to management interfaces that can push firmware images, and retire devices no longer receiving updates.

Tenda routers ship a hidden backdoor password with no patch available

CERT/CC has warned that several Tenda router firmware versions contain an undocumented authentication backdoor that grants full administrative access to the web management interface. Tracked as CVE-2026-11405, the flaw lives in the login function of the router's web server: if normal password checking fails, the firmware compares the supplied password against a hidden value stored in the device configuration and, on a match, grants admin access regardless of the username. It affects models including the FH1201, W15E, AC10, AC5, and AC6, is baked into the firmware, and cannot be disabled from the interface. Tenda has not responded, so there is no fix, and public exploit tooling is already scanning for vulnerable devices.

Check
Identify any Tenda routers in use, especially the affected FH1201, W15E, AC10, AC5, and AC6 models, and check whether the web management interface is reachable remotely or from untrusted networks.
Affected
Users of affected Tenda router models (CVE-2026-11405); anyone who can reach the web management interface can log in as administrator using a hidden backdoor password, with no valid credentials needed.
Fix
With no patch available, disable remote management, change the default LAN IP, restrict management access to trusted hosts, monitor for scanning on UDP port 7329, and plan to replace unsupported devices.

Seven flaws in the FatFs library expose millions of embedded devices, mostly unpatched

Researchers at runZero disclosed seven vulnerabilities in FatFs, a tiny filesystem library that lets devices read FAT and exFAT media like USB drives and SD cards and that is bundled into the firmware of countless embedded and industrial products. The most serious, CVE-2026-6682, is an integer overflow when mounting a FAT32 volume that can lead to memory corruption and code execution, and several bugs are reachable through firmware update flows, not just physical media. The hard part is patching: FatFs is maintained by a single developer who did not respond to the researchers, so most of the memory-corruption flaws have no upstream fix and downstream vendors may never learn they are affected.

Check
Inventory devices and firmware that bundle the FatFs library, especially anything that mounts USB, SD-card, or externally supplied filesystem images or accepts firmware updates, and ask vendors whether their products include FatFs.
Affected
Embedded, industrial, and consumer devices that bundle FatFs to read FAT or exFAT media (CVE-2026-6682 and six others); malicious media or update images can crash devices or corrupt memory toward code execution.
Fix
Where possible, restrict which USB, SD-card, and update-image sources a device will mount, isolate affected devices, and press vendors for firmware updates, since most of these flaws have no upstream fix.

Deploy 2023 Secure Boot certificates before Microsoft's 2011 ones expire this week

The original 2011 Microsoft certificates that underpin UEFI Secure Boot begin expiring in late June 2026, and organizations that have not rolled out the replacement 2023 certificates risk a slow erosion of boot-level security. Devices will keep starting normally, but once the old certificate authorities lapse they stop receiving Secure Boot updates for pre-boot components, leaving them more exposed to bootkits, and future bootloaders signed only with the new keys may fail to verify. Most consumer Windows PCs receive the 2023 certificates automatically through Windows Update, but Windows Server and many self-managed or older fleets need manual action. A second certificate that signs the Windows bootloader expires in October.

Check
Inventory Windows devices and servers with Secure Boot enabled and check whether the 2023 certificates are present using the Windows Security app, the UEFICA2023Status registry value, or System log Event ID 1808.
Affected
Windows devices, servers, and VMs still relying on the 2011 Secure Boot certificates; Windows Server and self-managed systems are most at risk because they do not receive the 2023 certificates automatically.
Fix
Apply current cumulative and OEM firmware updates, deploy the 2023 KEK and DB certificates (manually on servers), verify completion, and suspend BitLocker if prompted during the update to avoid recovery prompts.