Router vulnerability note - NETGEAR
NETGEAR RAX and Orbi: an assertion that takes the box down
What happened
The pair of advisories from October 2026 describe the same weakness reached from two directions: an assertion failure in the device's HTTP handling, unauthenticated on the RAX200/RAX52/RAX54/RAX75/RAX100/RAX220 and RS101 lines before the listed builds, and reachable by an authenticated user on the wider set including the RAX15, RAX20, RAX120, RAX240, RAXE500 and the RBK/ORBI mesh firmware. The consequence is the ordinary one — the device stops — and the fix versions are specific per model, which is the ordinary difficulty.
NETGEAR support matrices are the reason we tell owners to note the exact firmware string rather than the model. "RAX80" is not enough information; "1.0.4.144" is. On the Orbi and Nighthawk lines the same model number can be two hardware revisions behind, each with its own last build, and that is where a plan to "update it this weekend" turns into a search through three download pages.
Who is affected
RAX200 before 1.0.3.102, RS101 before 1.0.6.28, RAX52/RAX54/RAX75/RAX100/RAX220 before 1.3.07.44, RAX220 before 1.0.1.26 in the unauthenticated case; the authenticated case spans the earlier RAX and ORBI builds listed by NETGEAR.
Check it yourself
Firmware string, from the page rather than from memory
UI: Advanced > Administration > Router Update
# Firmware Version V1.0.4.104_10.0.65
$ curl -s -o /dev/null -w '%{http_code}\n' http://192.168.1.1/
# note the router's model *and* the build, both of them, in the audit sheet
Do this
- Update to the build named for your exact model, then re-check that the version string changed.
- If the router reboots by itself, look at the log for an assertion or a crash before blaming the ISP.
- On mesh systems, update satellite and router from the same release train.
- Write the firmware build on the label under the unit; it saves a phone call in three years.
How we handle it
NETGEAR devices rarely need a tunnel for us to help — the web UI is the whole job — but they do need reachability, so we ask for the admin credentials and a temporary port forward, or we work with you on the phone. Either way, the fix here is a download page and thirty minutes.