# Why Does an Unpatchable Router Flaw Matter to a 433 MHz Remote? **URL:** \ **Category:** News\ **Created:** [October 23, 2026, 9:40am UTC](https://rx480e.discourse.group/t/why-does-an-unpatchable-router-flaw-matter-to-a-433-mhz-remote/30 "2026-10-23T09:40:50Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Zercher](https://yyz2.discourse-cdn.com/flex012/user_avatar/rx480e.discourse.group/zercher/32/21_2.png) [@Zercher](https://rx480e.discourse.group/u/Zercher)\ **Post date:** [October 23, 2026, 9:40am UTC](https://rx480e.discourse.group/t/why-does-an-unpatchable-router-flaw-matter-to-a-433-mhz-remote/30/1 "2026-10-23T09:40:50Z")
The router in your hallway may never get a fix. ![image](https://canada1.discourse-cdn.com/flex012/uploads/rx480e/original/1X/610d31223755f2f7711ca7c125c8e4ef7ec38594.jpeg) On October 16, researcher Quentin Kaiser [disclosed](https://quentinkaiser.be/security/2026/10/16/one-parser-two-bugs/) a flaw in Broadcom’s Wi-Fi Protected Setup code. An attacker in radio range can run code as root on affected routers without the network password or pairing. No CVE was assigned. No fix has shipped. On the older chips he tested, he calls it a “forever day” — one that will never be patched. **Unpatchable only matters when something can reach it.** The 433 MHz remote on my bench has no software to patch. It also has no network stack, no password to read, and no shell to open. I press a button, a paired [RX480E-4](https://qiachip.github.io/qiachip/RX480E/RX480E-4/QIACHIP_RX480E-4/) switches one output pin. Nothing outside the room can log in. That is exactly why I like RF433. It is local by design: the button and the receiver talk to each other, and nothing on the network is involved. Nobody sitting on the other side of the planet has a path to it. So here is my question. When you read about router flaws like this one, does it make you want to move some of your devices off the network and onto RF433 instead?