The common thread across this week's security news is not a single vulnerability class or vendor. It is location. Attackers are increasingly operating at the layer people and companies treat as trustworthy by default, the kernel underneath the server, the hardware holding the keys, the router at the edge of the home network. When the trusted layer fails, everything built on top of it inherits the failure.
Root Before the Application
The most severe example is the Linux kernel flaw described by BleepingComputer, which allows unauthenticated attackers to remotely execute commands as root on servers running Multipath TCP listeners. The detail that matters is not just remote code execution. It is root, and it is unauthenticated. An exploit at that level bypasses the application-layer defenses most organizations have spent years buying and tuning. Web application firewalls, authentication gateways, and endpoint agents all assume a boundary between an untrusted request and a privileged system. A kernel-level flaw on a listening service dissolves that boundary entirely.
The source of the exploit work is also worth noting: researchers at Anthropic developed it, as BleepingComputer reported. That places a major AI company in the position of producing offensive tooling for core internet infrastructure. Whatever the intent, dual-use research of this kind compresses the window between disclosure and exploitation, and it signals that well-resourced organizations outside the traditional security-vendor ecosystem are now doing this work.
For US technology companies, the exposure is structural. Multipath TCP is a networking standard used to keep connections alive across multiple paths, and servers that listen for it are typically backend infrastructure, not customer-facing applications. These are the machines that sit behind the perimeter and are assumed to be protected by it. An unauthenticated root exploit on such a host is the worst-case scenario for incident response: the attacker has the same privileges as the administrator and can modify the kernel itself to persist.
The Wallet Is the Weak Point
Trezor's warning, also via BleepingComputer, describes a suspected hardware crypto-theft implant in a Trezor Safe 5 sold by a reseller, CryptoBilis, in Southeast Asia. This is a different mechanism but the same underlying pattern. A hardware wallet exists precisely to move trust out of general-purpose computers and into a dedicated device whose firmware and supply chain are supposed to be controlled. The reported implant compromises that assumption at the point of sale, through a reseller rather than the manufacturer.
That distinction matters for US consumers. The threat model for a hardware wallet has generally centered on phishing, seed-phrase theft, and malicious software on the user's computer. A tampered device delivered through a distribution channel attacks the one component the user was told to trust unconditionally. It also reframes the reseller as part of the security perimeter. Manufacturers can harden firmware and publish verification procedures, but they do not directly control what a third-party reseller ships in a box.
For US companies in the crypto custody space, the lesson extends beyond one vendor. Any product whose value proposition is physical trust, whether a wallet, a hardware security module, or an authenticated device, carries supply-chain risk that cannot be fully patched after the fact. Detection depends on users noticing something wrong and reporting it, which is exactly how this warning surfaced.
The Router at the Edge
The Netgear disclosure covered by ZDNET is the most modest of the three and, for that reason, the most representative. A vulnerability in some Netgear routers could allow an attacker with access to the network to run malicious commands on the device. The prerequisite, network access, limits severity compared with the Linux kernel flaw. But routers are the boundary device in millions of US homes and small businesses, frequently running outdated firmware, rarely monitored, and often administered with default credentials.
