CyberSecBulletin
CVE-2026-9212NVD status: Analyzed

Insufficient authentication and input validation in the listed NETGEAR models allow users…

Published Updated By the CyberSecBulletin desk

CVE-2026-9212 is a high-severity improper input validation vulnerability in LBR1020 from NETGEAR, with a CVSS 3.1 base score of 8.0 out of 10. It can be exploited from the same local network by an attacker with a low-privileged account, without any action from a user. The record lists version V2.6.4.60 as the first without the flaw, so updating LBR1020 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.27% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update LBR1020 to V2.6.4.60 or a later version.
  2. Update LBR20 to V2.7.6.8 or a later version.
  3. Update R7800 to V1.0.4.96 or a later version.
  4. Read the advisory on kb.netgear.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
NETGEARLBR1020before V2.6.4.60V2.6.4.60
NETGEARLBR20before V2.7.6.8V2.7.6.8
NETGEARR6700AXall versionsNot stated
NETGEARR7800before V1.0.4.96V1.0.4.96
NETGEARR9000before V1.0.6.46V1.0.6.46
NETGEARRAX10before V1.0.5.50V1.0.5.50
NETGEARRAX10v2before V1.0.5.50V1.0.5.50
NETGEARRAX120before V1.2.10.56V1.2.10.56
NETGEARRAX120v1before V1.2.10.56V1.2.10.56
NETGEARRAX120v2before V1.2.10.56V1.2.10.56
NETGEARRAX36Sbefore V1.0.5.50V1.0.5.50
NETGEARRAX70before V1.0.19.172V1.0.19.172
NETGEARRAX78before V1.0.19.172V1.0.19.172
NETGEARRBR10before 2.7.5.62.7.5.6
NETGEARRBR20before 2.7.5.62.7.5.6
NETGEARRBR350before V4.4.2.1V4.4.2.1
NETGEARRBR40before 2.7.5.62.7.5.6
NETGEARRBR50before 2.7.5.62.7.5.6
NETGEARRBS10before 2.7.5.62.7.5.6
NETGEARRBS20before 2.7.5.62.7.5.6
NETGEARRBS350before V4.4.2.1V4.4.2.1
NETGEARRBS40before 2.7.5.62.7.5.6
NETGEARRBS50before 2.7.5.62.7.5.6
NETGEARXR450before V2.3.3.136V2.3.3.136
NETGEARXR500before v2.3.3.136v2.3.3.136

Version data comes from the organisation that assigned the CVE; 22 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 4.05.6MediumCNA
CVSS 3.18.0HighNVD

Official description

Insufficient authentication and input validation in the listed NETGEAR models allow users connected to the local network to execute commands impacting the product's confidentiality or change certain configurations.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.