Last updated: September 29, 2026 at 8:42 AM UTC
All 891 Vulnerability 357 Breach 144 Threat 383 Defense 7
Tag: code-execution (12 articles)Clear

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.

Clean GitHub repos trick AI coding agents into fetching and running malware

Researchers at Mozilla's 0DIN found that an AI coding agent told to clone and set up a seemingly harmless GitHub repository can be tricked into running malware that stays invisible to security scanners, the agent itself, and human reviewers. The trick is that nothing malicious sits in the repository's files. Instead, a routine-looking setup command runs a script that fetches a value hidden in a DNS TXT record and executes it as a shell command, pulling down and running an attacker's payload like a reverse shell. Because the payload lives outside the repo and arrives over DNS at setup time, code review and static scanning see nothing wrong.

Check
Review how your AI coding agents and developers set up unfamiliar repositories, and check whether setup or build commands can make outbound network or DNS requests that fetch and execute external content.
Affected
Developers and teams that let AI coding agents automatically run setup steps for untrusted repositories; the malicious payload is fetched at setup time over DNS, so scanning the repository alone misses it.
Fix
Run repository setup for untrusted code in sandboxes without credentials, restrict outbound network and DNS during setup, and treat agent setup and build commands as untrusted code execution rather than safe automation.