CVE-2023-27361 is a stack-based buffer overflow in the way the NETGEAR RAX30 rex_cgi component parses JSON. NVD scores it 8.0, High, and a login is required. NETGEAR's advisory rates it Medium at 6.8 and lists firmware 1.0.9.92 as the fix. Update the router to that build or newer.
What's affected
NVD lists the NETGEAR RAX30 and RAXE300 as affected, as firmware and hardware entries without a version range. The advisory lists only the RAX30 and does not name vulnerable firmware builds.
Source conflict on severity: NVD scores this 8.0, High (vector CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). NETGEAR's own advisory (PSV-2022-0302, post-authentication buffer overflow) rates the issue Medium, with a CVSS 3.0 score of 6.8. This is the earliest fixed build in this group of NETGEAR RAX30 advisories. If you are already on 1.0.10.94 or later, you are past it.
How to check if you're exposed
Log in to the router's admin page, or open the NETGEAR Nighthawk app, and read the firmware version. Compare it with the fixed version above. Anything lower than the fixed build needs the update.
The advisory does not publish a list of vulnerable builds, so the fixed version is the only reliable cutoff. If you look after more than a few routers, build a simple list of model and firmware version for each one. These devices often sit in small offices and branch sites that never reach a central inventory.
What to do now
- Update the router to firmware 1.0.9.92 or later. NETGEAR recommends doing this as soon as possible, through the Nighthawk app or by downloading the build from NETGEAR Support for your model.
- Read the release notes for that firmware before installing, and finish all the steps NETGEAR lists. The advisory warns that the vulnerability remains if you skip any of them.
- Review who can reach the router's local network. Rotate the WiFi password if it has been shared widely, and keep guest devices on a separate network.
- Record the update in your asset list so you can show which routers are on the fixed build.
- Look up the CVE on its Gold page to follow changes in the score and references.
Why it matters
The record says the flaw comes from a missing length check on user-supplied data before it is copied into a fixed-length stack buffer. NVD classes it as CWE-121 (Stack-based Buffer Overflow) and CWE-787 (Out-of-bounds Write).
A stack overflow can overwrite data the program relies on to decide where to run next. That is why the record talks about code execution as root. Memory safety bugs in network-facing C code remain common in embedded devices, and the only dependable defence for owners is prompt firmware updates.
The phrase network-adjacent matters here. NVD scores the attack vector as adjacent, and NETGEAR's advisory says an attacker needs your WiFi password or an Ethernet connection to your network. That is a lower bar than a remote internet attack, but a higher bar than none. Guest WiFi, shared office space and a compromised laptop on the same network all shorten the distance.
Quick check
Why does a login requirement still matter for patching?
A login lowers the risk but does not remove it. Shared WiFi passwords and reused admin credentials are common on small networks, so the requirement is a weak barrier.
Sources
Last reviewed: 19 October 2026.