CVE-2026-11733
CVE-2026-11733 — Buffer overflow vulnerability in some NETGEAR Nighthawk routers
A buffer overflow vulnerability in the listed NETGEAR models allows a device administrator to temporarily interrupt the normal operation of the affected device.
Published Updated Sources: NVD, NETGEAR (CNA), GitHub, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Exploit code
public exploit, none observed
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
1.1
low
Remediation
The vendor's own words where we have them.
Devices with automatic updates enabled may already have this patch applied. If not, please check the firmware version and update it to the latest. Fixed in: ProductFixed VersionRAX41 (EoS) Nighthawk AX5 5-Stream AX3600 WiFi Router V1.1.6.36 https://www.netgear.com/support/product/rax41/ RAX41v2 Nighthawk AX5 5-Stream AX3600 WiFi Router V1.1.6.36 https://www.netgear.com/support/product/rax41v2/ RAX42 (EoS) Nighthawk AX5 5-Stream AX4200 WiFi Router V1.1.6.36 https://www.netgear.com/support/product/rax42/ RAX42v2 Nighthawk AX5 5-Stream AX4200 WiFi Router V1.1.6.36 https://www.netgear.com/support…
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| NETGEAR | RAX41 | 0 | Vulnerable |
| NETGEAR | RAX41v2 | 0 | Vulnerable |
| NETGEAR | RAX42 | 0 | Vulnerable |
| NETGEAR | RAX42v2 | 0 | Vulnerable |
| NETGEAR | RAX43 | 0 | Vulnerable |
| NETGEAR | RAX43v2 | 0 | Vulnerable |
| NETGEAR | RAX49S | 0 | Vulnerable |
| NETGEAR | RAX50 | 0 | Vulnerable |
| NETGEAR | RAX50v2 | 0 | Vulnerable |
| NETGEAR | RAX54S | 0 | Vulnerable |
| NETGEAR | RAX54Sv2 | 0 | Vulnerable |
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 1.1 | CVSS 4.0 | low | — | — | NETGEAR (CNA) |
CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U/AU:N/R:U/V:D/RE:L/U:Amber
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-121 · Stack-based Buffer Overflow
- Modify Memory
- DoS: Crash, Exit, or Restart
- DoS: Resource Consumption (CPU)
- DoS: Resource Consumption (Memory)
Mitigation: Run or compile the software using features or extensions that automatically provide a protection mechanism that mitigates or eliminates buffer overflows. For example, certain compilers and extensions provide automatic buffer overflow detection mechanisms that are built into the compiled code. Examples include the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice.
Weakness & attack patterns
- CWE-121
Inferred from the weakness class — not observed against this CVE.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
2
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Monitor for scanner or exploit-pattern traffic after 2 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 1.1
Aug 11, 2026 · NVD
Initial · CVE published
Aug 11, 2026 · NVD
References
9 on the record
- www.netgear.com/support/product/rax41/
Vendor Advisory
- www.netgear.com/support/product/rax41v2/
Vendor Advisory
- www.netgear.com/support/product/rax42/
Vendor Advisory
- www.netgear.com/support/product/rax42v2/
Vendor Advisory
- www.netgear.com/support/product/rax43/
Vendor Advisory
- www.netgear.com/support/product/rax43v2/
Vendor Advisory
- www.netgear.com/support/product/rax49s/
Vendor Advisory
- www.netgear.com/support/product/rax50/
Vendor Advisory
Elsewhere on this site
- NETGEARevery CVE for this vendor
- Remote Code Execsame class
- CWE-121other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-11733 is Buffer overflow vulnerability in some NETGEAR Nighthawk routers, a low vulnerability affecting RAX41, RAX41v2, RAX42, RAX42v2, RAX43, RAX43v2, RAX49S, RAX50, RAX50v2, RAX54S, RAX54Sv2 from NETGEAR. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-11733. Public exploit evidence is: 2 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 1.1 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.