Exploited CVEs / NETGEAR / CVE-2017-5521

CVE-2017-5521

NETGEAR Multiple Devices Exposure of Sensitive Information Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2022-09-29 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

Risk summary

HighCISA KEV
8.1
CVSS base
89%
EPSS exploit probability
High
Severity
2022-09-08
Added to KEV
2022-09-29 (past due)
CISA due date

Actively exploited NETGEAR Multiple Devices vulnerability, High severity, CVSS 8.1. Added to the CISA KEV catalog 2022-09-08.

Senserva AI read on CVE-2017-5521CISA required actionOfficial fix for CVE-2017-5521Admin questions

Senserva AI Opinion for CVE-2017-5521

A simple crafted request to the web management server on multiple NETGEAR devices discloses the admin password outright, no exploitation skill required. The 89% EPSS score and confirmed exploitation (KEV 2022-09-08) reflect how trivially this Severity High (CVSS 8.1) flaw is automated by scanners and botnets. Once the admin password is out, the attacker owns the router and everything behind it.

Do this: Check all NETGEAR routers and access points for current firmware and disable remote web management on every one of them.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2017-5521

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Federal remediation deadline 2022-09-29; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2017-5521

Published
2022-09-08
Last revised
2022-09-08
Changes tracked
1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when
  • 2022-09-08 added to the CISA KEV catalog by CISA
  • 2026-07-17 CVSS 0.0 to 8.1; EPSS first scored at 89.3%
  • 2026-07-23 EPSS 89.3% to 89.3%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2022-09-29 (past due).

Apply updates per vendor instructions. If the affected device has since entered end-of-life, it should be disconnected if still in use.

Official fix for CVE-2017-5521

Check the vendor's security advisory channel for the patched Multiple Devices versions and workarounds.

Common questions about CVE-2017-5521

Is CVE-2017-5521 actively exploited?

Yes. CVE-2017-5521 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2022-09-08, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 89%.

What is the CISA deadline and required action for CVE-2017-5521?

CISA set the federal (BOD 22-01) remediation due date at 2022-09-29, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply updates per vendor instructions. If the affected device has since entered end-of-life, it should be disconnected if still in use.

What fixes CVE-2017-5521?

Check the vendor's security advisory for the patched Multiple Devices versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2017-5521?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2017-5521's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.