CVE-2020-26913 [Medium] | Out-of-bounds Write in D6100 Firmware

Certain NETGEAR devices are affected by a stack-based buffer overflow by an authenticated user. This affects D6100 before 1.0.0.63, R7800 before 1.0.2.60, R8900 before 1.0.4.26, R9000 before 1.0.4.26, RBK20 before 2.3.0.28, RBR20 before 2.3.0.28, RBS20 before 2.3.0.28, RBK50 before 2.3.0.32, RBR50 before 2.3.0.32, RBS50 before 2.3.0.32, RBK40 before 2.3.0.28, RBR40 before 2.3.0.28, RBS40 before 2.3.0.28, SRK60 before 2.2.2.20, SRR60 before 2.2.2.20, SRS60 before 2.2.2.20, WN3000RPv2 before 1.0.0.78, WNDR4300v2 before 1.0.0.58, WNDR4500v3 before 1.0.0.58, WNR2000v5 before 1.0.0.70, XR450 before 2.3.2.40, and XR500 before 2.3.2.40.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.31%	0.56%	+0.24%
2	2025-11-21	0.14%	0.31%	+0.17%
3	2025-11-18	—	0.14%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.31%

0.56%

+0.24%

2025-11-21

0.14%

0.31%

+0.17%

2025-11-18

—

0.14%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.8	3.1	MEDIUM	`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	0.9	5.9	[email protected]
6.8	3.1	MEDIUM	`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	0.9	5.9	[email protected]
5.2	2.0	MEDIUM	`AV:A/AC:L/Au:S/C:P/I:P/A:P` Click to expand Access vector (AV:A) Requires access to an adjacent network segment. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:S) A single authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	5.1	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.8

3.1

MEDIUM

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

0.9

5.9

[email protected]

6.8

3.1

MEDIUM

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

0.9

5.9

[email protected]

5.2

2.0

MEDIUM

AV:A/AC:L/Au:S/C:P/I:P/A:P Click to expand

Access vector (AV:A): Requires access to an adjacent network segment.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:S): A single authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

5.1

6.4

[email protected]

Affected software / configurations for CVE-2020-26913

Vendor	Product	Version	Raw CPE
netgear	d6100_firmware	< 1.0.0.63	cpe:2.3:o:netgear:d6100_firmware::::::::
netgear	r7800_firmware	< 1.0.2.60	cpe:2.3:o:netgear:r7800_firmware::::::::
netgear	r8900_firmware	< 1.0.4.26	cpe:2.3:o:netgear:r8900_firmware::::::::
netgear	r9000_firmware	< 1.0.4.26	cpe:2.3:o:netgear:r9000_firmware::::::::
netgear	rbk20_firmware	< 2.3.0.28	cpe:2.3:o:netgear:rbk20_firmware::::::::
netgear	rbr20_firmware	< 2.3.0.28	cpe:2.3:o:netgear:rbr20_firmware::::::::
netgear	rbs20_firmware	< 2.3.0.28	cpe:2.3:o:netgear:rbs20_firmware::::::::
netgear	rbk50_firmware	< 2.3.0.32	cpe:2.3:o:netgear:rbk50_firmware::::::::
netgear	rbr50_firmware	< 2.3.0.32	cpe:2.3:o:netgear:rbr50_firmware::::::::
netgear	rbs50_firmware	< 2.3.0.32	cpe:2.3:o:netgear:rbs50_firmware::::::::
netgear	rbk40_firmware	< 2.3.0.28	cpe:2.3:o:netgear:rbk40_firmware::::::::
netgear	rbs40_firmware	< 2.3.0.28	cpe:2.3:o:netgear:rbs40_firmware::::::::
netgear	srk60_firmware	< 2.2.2.20	cpe:2.3:o:netgear:srk60_firmware::::::::
netgear	srr60_firmware	< 2.2.2.20	cpe:2.3:o:netgear:srr60_firmware::::::::
netgear	srs60_firmware	< 2.2.2.20	cpe:2.3:o:netgear:srs60_firmware::::::::
netgear	wn3000rpv2_firmware	< 1.0.0.78	cpe:2.3:o:netgear:wn3000rpv2_firmware::::::::
netgear	wndr4300v2_firmware	< 1.0.0.58	cpe:2.3:o:netgear:wndr4300v2_firmware::::::::
netgear	wndr4500v3_firmware	< 1.0.0.58	cpe:2.3:o:netgear:wndr4500v3_firmware::::::::
netgear	wnr2000v5_firmware	< 1.0.0.70	cpe:2.3:o:netgear:wnr2000v5_firmware::::::::
netgear	xr450_firmware	< 2.3.2.40	cpe:2.3:o:netgear:xr450_firmware::::::::
netgear	xr500_firmware	< 2.3.2.40	cpe:2.3:o:netgear:xr500_firmware::::::::

References for CVE-2020-26913

URL	Tags
https://kb.netgear.com/000062340/Security-Advisory-for-Post-Authentication-Stack-Overflow-on-Some-Routers-and-WiFi-Systems-PSV-2018-0140	Vendor Advisory

URL

CVE-2020-26913

Exploit prediction scoring system (EPSS) score for CVE-2020-26913

Common vulnerability scoring system (CVSS) metrics for CVE-2020-26913

Weakness enumeration for CVE-2020-26913

Affected software / configurations for CVE-2020-26913

References for CVE-2020-26913